-
Notifications
You must be signed in to change notification settings - Fork 57
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
perfect 'docker-compose.yml' file #78
Comments
|
Can you post your docker-compose.yml? Also yes, internal is port 5000 |
|
Are you accessing on https://www.example.com:5000/admin or https://www.example.com:5000? |
You may just need to remove :5000 from the |
I understand what you mean. In actual testing, I used the complete path |
My headscale has enabled the HTTPS+443 port internally and is configured with a TLS certificate
headscale-config.yaml
|
I visited before https://www.example.com:5000/admin |
I think I see the problem... Are you using a reverse proxy?
The container serves on http. Maybe http://example.com:5000 would work?
On April 8, 2023 4:17:07 PM UTC, threerog ***@***.***> wrote:
> Are you accessing on https://www.example.com:5000/admin or https://www.example.com:5000?
I visited before https://www.example.com:5000/admin
but
I have now deleted SCRIPT_ NAME content, direct access https://www.example.com:5000
It's still the same mistake as before
--
Reply to this email directly or view it on GitHub:
#78 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
--
Albert J. Copeland
***@***.***
PGP Fingerprint: 64F6C4EB46C4543A
|
Hm, no I see it's erroring on getting the healthcheck from Headscale... |
I seem to have found the problem, suspected to be caused by curl's Is the underlying layer of
This is an article sent to me by a colleague |
After I discovered that it was suspected to be related to curl, I attempted to upgrade the curl software package but still failed. But I tested the |
This I am clueless on. I just use the plain ol' Python requests library for all the HTTP requests |
Which I guess is HTTP/1.1? |
I am also at a loss. My new server synchronizes according to the same configuration and image of the old server, but in the end, one server succeeds while the other fails. |
I'm sorry, it's not an issue with |
https://github.com/iFargle/headscale-webui/blob/main/docker-compose.yml
Incomplete document information
Incomplete parameter information
HS_ SERVER is https://www.example.com Unable to work at time
But I opened it https://www.example.com/swagger Normal access
and opened it https://www.example.com/health Normal access
Also, is the internal port of webui fixed at 5000?
The text was updated successfully, but these errors were encountered: