mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
500 error when trying to setup reverse-proxy with SSL (Apache) #373
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#373
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mangokinky on GitHub (Oct 10, 2021).
Is it a duplicate question?
Please search in Issues without filters: https://github.com/louislam/uptime-kuma/issues?q=
I couldn't find any issue with this problem
Describe your problem
Hello, I'm trying to setup Reverse-Proxy with SSL using Apache for Uptime-Kuma
But I get 500 Internal Server Error, I double-checked that I did everything correctly but the error is still there
Info
Uptime Kuma Version: 1.7.3
Using Docker?: No
Docker Version: //
Node.js Version (Without Docker only): v16.11.0
OS: Ubuntu 2004
Browser: Chrome
@louislam commented on GitHub (Oct 10, 2021):
You have to provide apache log and the apache config
@mangokinky commented on GitHub (Oct 10, 2021):
Error:
Config:
@mangokinky commented on GitHub (Oct 10, 2021):
nwm, found the issue
For anyone wondering I found the solution here
@mangokinky commented on GitHub (Oct 10, 2021):
Hello, I have another problem, now I can't use dashboard because it says this:
Cannot connect to the socket server. [Error: websocket error] Reconnecting...
@louislam commented on GitHub (Oct 10, 2021):
If localhost is working, it is usually because of missing the upgrade headers.
@mangokinky commented on GitHub (Oct 10, 2021):
Yes, localhost is working, could you please tell me how to add the upgrade headers?
@chakflying commented on GitHub (Oct 10, 2021):
From this answer looks like you need
proxy_wstunnelmodule as well. Have you checked you have installed it?@mangokinky commented on GitHub (Oct 10, 2021):
I didn't, I'll try it out right after I get back
Thanks for showing me!
@mangokinky commented on GitHub (Oct 10, 2021):
Yes it's working, thank you so much!