Show Posts
1
24.7 Production Series / SSL_ERROR_INTERNAL_ERROR_ALERT
« on: August 11, 2024, 08:58:44 pm »
I've been running Opnsense for a while with no issues and recently have created a new machine for a friend. The machine is hardware identical with the setup being a near copy of mine, save the inclusion of Caddy to reverse proxy to a Proxmox/Jellyfin instance.
Everything was working fine last night, but this morning Jellyfin didn't work and I could get into the Opnsense GUI. I was able to 'fix' Jellyfin by deleting /etc/ssl/jellyfin/cert.pfx through a Proxmox console, but I can't get into Opnsense at all. Trying to go to 192.168.1.1 gives a "SSL_ERROR_INTERNAL_ERROR_ALERT" with no option to, as was previously the case when accessing that IP and getting a (presumably slightly different) error, accept the risk.
Opnsense is working fine, including the reverse proxy from outside my network, I just can't get into the GUI -- I have tried different OSes (Fedora, Windows, Android) and browsers (firefox, Librefox, Brave). I have been able to connect a display and keyboard to the machine and get a command prompt, but I don't know what to do from there, short of wiping the machine and starting over, to get it to go back to allowing Http.
Any suggestions would be appreciated.
Addendum Using keyboard/display attached to the machine and running "configctl webgui restart renew" results in "unable to connect to configd socket (@/var/run/configd.socket)".
Everything was working fine last night, but this morning Jellyfin didn't work and I could get into the Opnsense GUI. I was able to 'fix' Jellyfin by deleting /etc/ssl/jellyfin/cert.pfx through a Proxmox console, but I can't get into Opnsense at all. Trying to go to 192.168.1.1 gives a "SSL_ERROR_INTERNAL_ERROR_ALERT" with no option to, as was previously the case when accessing that IP and getting a (presumably slightly different) error, accept the risk.
Opnsense is working fine, including the reverse proxy from outside my network, I just can't get into the GUI -- I have tried different OSes (Fedora, Windows, Android) and browsers (firefox, Librefox, Brave). I have been able to connect a display and keyboard to the machine and get a command prompt, but I don't know what to do from there, short of wiping the machine and starting over, to get it to go back to allowing Http.
Any suggestions would be appreciated.
Addendum Using keyboard/display attached to the machine and running "configctl webgui restart renew" results in "unable to connect to configd socket (@/var/run/configd.socket)".