Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mapping to subDomain #4593

Closed
2 tasks done
PaulMcF1987 opened this issue Mar 18, 2024 · 3 comments
Closed
2 tasks done

Mapping to subDomain #4593

PaulMcF1987 opened this issue Mar 18, 2024 · 3 comments
Labels
area:deployment related to how uptime kuma can be deployed help Stale

Comments

@PaulMcF1987
Copy link

⚠️ Please verify that this question has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ 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 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:
@CommanderStorm
Copy link
Collaborator

Really unclear what is missing in your case.

Let's try to debug this:

  • What are the network requests going on in your browsers console?
  • what are the respective logs of uptime Kuma or the reverse proxy's?

@CommanderStorm CommanderStorm added the area:deployment related to how uptime kuma can be deployed label Mar 18, 2024
@DuncanBennie
Copy link

I had this when I was hosting behind Cloudflare and hadn't enabled websockets. If you're using Cloudflare, make sure you enable websockets: https://developers.cloudflare.com/network/websockets/

Copy link

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.

@github-actions github-actions bot added the Stale label May 19, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:deployment related to how uptime kuma can be deployed help Stale
Projects
None yet
Development

No branches or pull requests

3 participants