I get no error message (login successful) but I am stuck on the login screens. Looking at the debug console I can see the call was indeed successful, but the Set-Cookie header restrict to httpOnly, but I am on httpS, and the dynamic config forces me to use HTTPS (and I want HTTPS).
Did I miss something?
I am using fosrl/pangolin:1.0.0-beta.6
Originally created by @francisbr on GitHub (Jan 17, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/67
I just started a fresh setup using the 'Manual Install' & 'Without Tunneling' pages from the doc. After the docker stacks boots up:
1. I go to https://proxy.<my_domain>/
2. Enter the default user information
- admin@example.com
- Password123!
I get no error message (login successful) but I am stuck on the login screens. Looking at the debug console I can see the call was indeed successful, but the Set-Cookie header restrict to httpOnly, but I am on httpS, and the dynamic config forces me to use HTTPS (and I want HTTPS).
Did I miss something?
I am using `fosrl/pangolin:1.0.0-beta.6`
What is your base_domain set to in the Pangolin config file? Looks like the Set-Cookie header is setting the cookie for the .localhost domain, so my guess is base_domain is set to localhost.
<!-- gh-comment-id:2597342591 -->
@miloschwartz commented on GitHub (Jan 17, 2025):
What is your `base_domain` set to in the Pangolin config file? Looks like the Set-Cookie header is setting the cookie for the `.localhost` domain, so my guess is `base_domain` is set to localhost.
Indeed! this is what I missed! thank you very much!
Maybe a small step should be added in the doc to tell to update this value? or a comment in the auto-generated file like the other ones to identify where I need to put my domain?
<!-- gh-comment-id:2597355062 -->
@francisbr commented on GitHub (Jan 17, 2025):
Indeed! this is what I missed! thank you very much!
Maybe a small step should be added in the doc to tell to update this value? or a comment in the auto-generated file like the other ones to identify where I need to put my domain?
Maybe a small step should be added in the doc to tell to update this value? or a comment in the auto-generated file like the other ones to identify where I need to put my domain?
Ah good point. I added a note to update the config file at the bottom for now. Thanks for the pointing this out :)
<!-- gh-comment-id:2597363222 -->
@miloschwartz commented on GitHub (Jan 17, 2025):
> Maybe a small step should be added in the doc to tell to update this value? or a comment in the auto-generated file like the other ones to identify where I need to put my domain?
Ah good point. I added a note to update the config file at the bottom for now. Thanks for the pointing this out :)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @francisbr on GitHub (Jan 17, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/67
I just started a fresh setup using the 'Manual Install' & 'Without Tunneling' pages from the doc. After the docker stacks boots up:
I get no error message (login successful) but I am stuck on the login screens. Looking at the debug console I can see the call was indeed successful, but the Set-Cookie header restrict to httpOnly, but I am on httpS, and the dynamic config forces me to use HTTPS (and I want HTTPS).
Did I miss something?
I am using
fosrl/pangolin:1.0.0-beta.6@miloschwartz commented on GitHub (Jan 17, 2025):
What is your
base_domainset to in the Pangolin config file? Looks like the Set-Cookie header is setting the cookie for the.localhostdomain, so my guess isbase_domainis set to localhost.@francisbr commented on GitHub (Jan 17, 2025):
Indeed! this is what I missed! thank you very much!
Maybe a small step should be added in the doc to tell to update this value? or a comment in the auto-generated file like the other ones to identify where I need to put my domain?
@miloschwartz commented on GitHub (Jan 17, 2025):
Ah good point. I added a note to update the config file at the bottom for now. Thanks for the pointing this out :)