-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Unable to connect to the local headscale-ui, there is a problem with the APIKEY #97
Comments
you're connecting on 6060 and on http. 6060 is not a standard https port. Are you sure CORS is configured correctly? If you're using a reverse proxy there is no reason to connect on port 6060. |
For the Headscale server, I did not use a reverse proxy. Currently, I use the domain name + port to access, such as https://google.com:6060/windows, which can be accessed normally. Thank you for your help |
from the front page: Errors related to "Missing Bearer Prefix" Alternatively, you haven't fixed your domain. HS-UI has to be ran on the same subdomain or you need to configure CORS. Yes you need to use a reverse proxy to do this. Use a reverse proxy. |
closing as question has been answered |
** Supporting Details **
Provide the following:
control+shift+i
in chrome to see)TypeError: Failed to fetch
I did not use the installation method of docker composer to install
I downloaded the latest version of headscale-ui and uploaded it to the server directory
Then achieve the effect of accessing the headscale-ui setting page through Nginx
But when visiting the home page, he will prompt: TypeError: Failed to fetch
Then I enter the APIKEY on the setting page, but I still can't connect successfully
Through the network module of F12, it is found that the request address of many of its contents is 127.0.0.1:7890
But the port 7890 is not monitored locally, the actual port should be 6060
Can't find where to change this setting
i don't know what to do
`#HeadscaleUI
server {
#listen 80;
listen 443 ssl;
server_name vpn.baidu.top;
}`
The text was updated successfully, but these errors were encountered: