and an nginx reverse proxy in a different container redirecting there:
\nserver{\n server_name subdomain.domain.tld;\n location /{\n proxy_pass http://x.y.z.w:8080/;\n proxy_set_header Host $http_host;\n proxy_set_header Upgrade $http_upgrade;\n proxy_set_header Connection upgrade;\n proxy_set_header Accept-Encoding gzip;\n }\n\n\n listen 443 ssl; # managed by Certbot\n # ...\n
This worked for a bit, but after changing the password for code-server, I am now experiencing a login-loop where entering a correct password drops me into the same login screen again with no feedback in either the web interface nor stdout . Incorrect password entries are detected and reported.
\nIt does work when I access via local IP.
","upvoteCount":1,"answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"Upon further investigation, this seems to be an issue with local browser data. I had tried with both firefox and chromium and the issue persisted when just clearing cache. After having success from a different machine, I tried deleting all browser data for that site, which worked on both browsers.
\nThe problem is therefore resolved for me.
","upvoteCount":1,"url":"https://github.com/coder/code-server/discussions/6635#discussioncomment-8274257"}}}-
Hello, I have code-server running in a LXC container with the following config:
and an nginx reverse proxy in a different container redirecting there:
This worked for a bit, but after changing the password for code-server, I am now experiencing a login-loop where entering a correct password drops me into the same login screen again with no feedback in either the web interface nor stdout . Incorrect password entries are detected and reported. It does work when I access via local IP. |
Beta Was this translation helpful? Give feedback.
-
Upon further investigation, this seems to be an issue with local browser data. I had tried with both firefox and chromium and the issue persisted when just clearing cache. After having success from a different machine, I tried deleting all browser data for that site, which worked on both browsers. The problem is therefore resolved for me. |
Beta Was this translation helpful? Give feedback.
Upon further investigation, this seems to be an issue with local browser data. I had tried with both firefox and chromium and the issue persisted when just clearing cache. After having success from a different machine, I tried deleting all browser data for that site, which worked on both browsers.
The problem is therefore resolved for me.