kkirk
November 13, 2023, 12:42pm
1
Hello,
I’m very vanilla and inherited this system. I upgraded for our Domain controllers from 2012 → 2022 now receiving this message.
http: proxy error: dial tcp: lookup (internalwebsite.com ): No address associated with hostname\n
Would restarting services for the server fix the issue or is it something else?
Any input is appreciated, currently working through this.
kkirk
November 13, 2023, 12:55pm
2
Seems like a certificate for the internal web server isnt on the new DC? Maybe?
kkirk
November 13, 2023, 6:04pm
3
I’m into the server via ssh, but really don’t know where to begin.
kkirk
November 15, 2023, 1:19pm
4
So after restarting and looking into logs…
Web server certificate error
Does anyone know what to do in this situation?
I’ve been researching to no avail.
Found this in documentation.
If a hostname is used in Pritunl Zero the internal server must have a valid certificate.
Is this in reference to the SSL cert for the internal webserver?
zach
November 16, 2023, 9:54pm
5
For most configurations the internal server should be an IP address. If it is a domain it will require the internal server to return a valid certificate. You can run sudo pritunl-zero set router skip_verify true
to ignore invalid certificates on internal servers.
kkirk
December 1, 2023, 6:41pm
6
Unfortunately this didn’t work.
zach
December 1, 2023, 10:17pm
7
I need the full error message to see specifically what error is occurring.
kkirk
December 4, 2023, 7:09pm
9
What log file should I look up?