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 am hosting uptime-kuma on docker
When I run the container via port:ip it works fine.
I have mapped the port to a subdomain https://my.domain.co.uk
The page loads but there is a red banner at the top which says Cannot connect to the socket server. [Error: websocket error] Reconnecting... Using a Reverse Proxy? [Check how to config it for WebSocket](https://github.com/louislam/uptime-kuma/wiki/Reverse-Proxy)
I have views this page and tried both the caddy and https-portal options, none of which work, and leave me in the same position
Any help would be much appreciated.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.22.1
💻 Operating System and Arch
Ubuntu 20.04.6 LTS
🌐 Browser
Sidekick
🖥️ Deployment Environment
Runtime:
Database:
Filesystem used to store the database on:
number of monitors:
The text was updated successfully, but these errors were encountered:
We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.
🛡️ Security Policy
📝 Describe your problem
I am hosting uptime-kuma on docker
When I run the container via
port:ip
it works fine.I have mapped the port to a subdomain
https://my.domain.co.uk
The page loads but there is a red banner at the top which says
Cannot connect to the socket server. [Error: websocket error] Reconnecting... Using a Reverse Proxy? [Check how to config it for WebSocket](https://github.com/louislam/uptime-kuma/wiki/Reverse-Proxy)
I have views this page and tried both the
caddy
andhttps-portal
options, none of which work, and leave me in the same positionAny help would be much appreciated.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.22.1
💻 Operating System and Arch
Ubuntu 20.04.6 LTS
🌐 Browser
Sidekick
🖥️ Deployment Environment
The text was updated successfully, but these errors were encountered: