Cannot access GUI via https

[eperk-tech]

I can't seem to bring up the web gui and it appears to be ssl related

* Trying 10.1.6.6:8006...
* Connected to 10.1.6.6 (10.1.6.6) port 8006 (#0)
* schannel: disabled automatic use of client certificate
* schannel: using IP address, SNI is not supported by OS.
* ALPN: offers http/1.1
* Recv failure: Connection was reset
* schannel: failed to receive handshake, SSL/TLS connection failed
* Closing connection 0
* schannel: shutting down SSL/TLS connection with 10.1.6.6 port 8006
* Send failure: Connection was reset
* schannel: failed to send close msg: Failed sending data to the peer (bytes written: -1)
curl: (35) Recv failure: Connection was reset



I followed the Prox doc on rebuilding certificates and still the same issue


Logs:
Jul 30 17:08:49 virtualenv01 pveproxy[7341]: worker 7343 started
Jul 30 17:08:49 virtualenv01 pveproxy[7341]: worker 7344 started
Jul 30 17:08:49 virtualenv01 systemd[1]: Started PVE API Proxy Server.
Jul 30 17:08:56 virtualenv01 systemd[1]: Stopping PVE API Daemon...
Jul 30 17:08:58 virtualenv01 pvedaemon[1031]: received signal TERM
Jul 30 17:08:58 virtualenv01 pvedaemon[1031]: server closing
Jul 30 17:08:58 virtualenv01 pvedaemon[1034]: worker exit
Jul 30 17:08:58 virtualenv01 pvedaemon[1033]: worker exit
Jul 30 17:08:58 virtualenv01 pvedaemon[1032]: worker exit
Jul 30 17:08:58 virtualenv01 pvedaemon[1031]: worker 1032 finished
Jul 30 17:08:58 virtualenv01 pvedaemon[1031]: worker 1034 finished
Jul 30 17:08:58 virtualenv01 pvedaemon[1031]: worker 1033 finished
Jul 30 17:08:58 virtualenv01 pvedaemon[1031]: server stopped
Jul 30 17:08:59 virtualenv01 systemd[1]: pvedaemon.service: Succeeded.
Jul 30 17:08:59 virtualenv01 systemd[1]: Stopped PVE API Daemon.
Jul 30 17:08:59 virtualenv01 systemd[1]: pvedaemon.service: Consumed 3.654s CPU time.
Jul 30 17:08:59 virtualenv01 systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
Jul 30 17:08:59 virtualenv01 systemd[1]: Starting PVE API Daemon...
Jul 30 17:09:00 virtualenv01 pvedaemon[7375]: starting server
Jul 30 17:09:00 virtualenv01 pvedaemon[7375]: starting 3 worker(s)
Jul 30 17:09:00 virtualenv01 pvedaemon[7375]: worker 7376 started
Jul 30 17:09:00 virtualenv01 pvedaemon[7375]: worker 7377 started
Jul 30 17:09:00 virtualenv01 pvedaemon[7375]: worker 7378 started
Jul 30 17:09:00 virtualenv01 systemd[1]: Started PVE API Daemon.
Jul 30 17:17:01 virtualenv01 CRON[8446]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 30 17:17:01 virtualenv01 CRON[8447]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 30 17:17:01 virtualenv01 CRON[8446]: pam_unix(cron:session): session closed for user root
Jul 30 17:22:34 virtualenv01 smartd[696]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel ch>
Jul 30 17:22:34 virtualenv01 smartd[696]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius change>



The service looks good from what I can tell:

Jul 30 17:08:49 virtualenv01 pveproxy[7341]: worker 7343 started
Jul 30 17:08:49 virtualenv01 pveproxy[7341]: worker 7344 started
Jul 30 17:08:49 virtualenv01 systemd[1]: Started PVE API Proxy Server.
Jul 30 17:08:56 virtualenv01 systemd[1]: Stopping PVE API Daemon...
Jul 30 17:08:58 virtualenv01 pvedaemon[1031]: received signal TERM
Jul 30 17:08:58 virtualenv01 pvedaemon[1031]: server closing
Jul 30 17:08:58 virtualenv01 pvedaemon[1034]: worker exit
Jul 30 17:08:58 virtualenv01 pvedaemon[1033]: worker exit
Jul 30 17:08:58 virtualenv01 pvedaemon[1032]: worker exit
Jul 30 17:08:58 virtualenv01 pvedaemon[1031]: worker 1032 finished
Jul 30 17:08:58 virtualenv01 pvedaemon[1031]: worker 1034 finished
Jul 30 17:08:58 virtualenv01 pvedaemon[1031]: worker 1033 finished
Jul 30 17:08:58 virtualenv01 pvedaemon[1031]: server stopped
Jul 30 17:08:59 virtualenv01 systemd[1]: pvedaemon.service: Succeeded.
Jul 30 17:08:59 virtualenv01 systemd[1]: Stopped PVE API Daemon.
Jul 30 17:08:59 virtualenv01 systemd[1]: pvedaemon.service: Consumed 3.654s CPU time.
Jul 30 17:08:59 virtualenv01 systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
Jul 30 17:08:59 virtualenv01 systemd[1]: Starting PVE API Daemon...
Jul 30 17:09:00 virtualenv01 pvedaemon[7375]: starting server
Jul 30 17:09:00 virtualenv01 pvedaemon[7375]: starting 3 worker(s)
Jul 30 17:09:00 virtualenv01 pvedaemon[7375]: worker 7376 started
Jul 30 17:09:00 virtualenv01 pvedaemon[7375]: worker 7377 started
Jul 30 17:09:00 virtualenv01 pvedaemon[7375]: worker 7378 started
Jul 30 17:09:00 virtualenv01 systemd[1]: Started PVE API Daemon.
Jul 30 17:17:01 virtualenv01 CRON[8446]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 30 17:17:01 virtualenv01 CRON[8447]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 30 17:17:01 virtualenv01 CRON[8446]: pam_unix(cron:session): session closed for user root
Jul 30 17:22:34 virtualenv01 smartd[696]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel ch>
Jul 30 17:22:34 virtualenv01 smartd[696]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius change>



Any Thoughts?

 

[Zerstoiber]

sounds like two things
a) it's not working in a browser on your remote machine
then you probably have a networking related misconfiguration and we need more details

b) you try to troubleshoot with CURL
from what machine?
what is your curl command, are you using the -k to ignore certificate errors?
https://curl.se/docs/manpage.html#-k

 

[eperk-tech]

Below is the curl command I ran

curl -v -k https://10.1.6.6:8006 -k

I get the same error whether I'm on a different network separated by FW or on the same subnet with direct Layer 2 access.