Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

v3.1.0 doesn't work for me - Can't log in

See original GitHub issue

Hi, I’ve just updated from an older 2.x version to v3.1.0 but I cannot login. It keeps redirecting me from / to /login?to=%2F. I downgraded to v3.0.2 and that works fine. Only lead I can give is that this error is logged in chrome:

The service worker navigation preload request was cancelled before ‘preloadResponse’ settled. If you intend to use ‘preloadResponse’, use waitUntil() or respondWith() to wait for the promise to settle.

Issue Analytics

State:
Created 3 years ago
Comments:13 (7 by maintainers)

Top GitHub Comments

1reaction

code-ashercommented, Apr 13, 2020

Oh hmm one thing that changed in 3.1.0 was that we added the domain to the cookie. It’ll use the host header. If it’s blank or not set it won’t set the domain (that will result in the same behavior as pre-3.1.0), otherwise it’ll use the host header directly as the domain.

Does your nginx configuration do anything interesting with the host header, maybe?

0reactions

code-ashercommented, Apr 14, 2020

Oh, yeah, I can see how that flag would be confusing! For anyone that’s curious, the --proxy-domain flag is for configuring code-server’s own built-in proxy and won’t affect behavior with external proxies like nginx.

I’ve just tagged 3.1.1 so we’ll have a release with this fix out soon so the host header will no longer be required for logging in. Although it’s probably not a bad idea to forward the host information anyway. 😃