You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I currently run all my espurna devices inside a separate LAN, with no forwarding to WAN.
My setup involves a pfsense router with reverse proxy for accessing everything I need inside the LAN, over HTTPS only.
From time to time however I need to do some admin over the internet, so I have setup a reverse proxy rule that I can easily change to point to a specific espurna device.
Problem is when connecting over HTTPS, rev.proxy connects over HTTP to the espurna. Page is served but when webservices are called, they are called over HTTP (ws://....) so they end up nowhere.
Error received after logging in:
Mixed Content: The page at 'https://xxxxxx.com/' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://xxxxxx.com/ws'. This request has been blocked; this endpoint must be available over WSS.
A workaround could be to detect if we are HTTP or HTTPS and request the WS accordingly.
What do you think?
The text was updated successfully, but these errors were encountered:
hyteoo
changed the title
web ui does not work over HTTPS when connecting from outside LAN with reverse proxy
web ui does not work over HTTPS when connecting from outside the LAN with reverse proxy
Jun 14, 2018
hyteoo
changed the title
web ui does not work over HTTPS when connecting from outside the LAN with reverse proxy
web ui does not work over HTTPS when connecting from outside the LAN through reverse proxy
Jun 14, 2018
I currently run all my espurna devices inside a separate LAN, with no forwarding to WAN.
My setup involves a pfsense router with reverse proxy for accessing everything I need inside the LAN, over HTTPS only.
From time to time however I need to do some admin over the internet, so I have setup a reverse proxy rule that I can easily change to point to a specific espurna device.
Problem is when connecting over HTTPS, rev.proxy connects over HTTP to the espurna. Page is served but when webservices are called, they are called over HTTP (ws://....) so they end up nowhere.
Error received after logging in:
Mixed Content: The page at 'https://xxxxxx.com/' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://xxxxxx.com/ws'. This request has been blocked; this endpoint must be available over WSS.
A workaround could be to detect if we are HTTP or HTTPS and request the WS accordingly.
What do you think?
The text was updated successfully, but these errors were encountered: