Caddy Community Google OAuth broken?

(Ferdinand Mütsch) #1

I tried to sign up via Google OAuth, but got the following error. Might this be an issue with the login mechanism?

(Toby Allen) #2

I think this may be a race condition with the new website. Try from

(Matt Holt) #3

Yeah, how’d you get the new domain name? :wink:

Gimme another day or two to get all the properties transferred over.

(Matt Holt) #4

Ah nevermind, I just went ahead and did the switch. You’ll have to log in again, sorry about that. But let me know if anything doesn’t work!

(Ferdinand Mütsch) #5

Works like a charm now, thank you :thumbsup:
By the way, I really like this forum software. Although the community forum is not served by Caddy :smile:

how’d you get the new domain name?

You posted it on Twitter :wink:

(Matt Holt) #6

Great! Yeah, I like Discourse.

It actually is :wink: I wrote up this example after fronting Discourse with Caddy:

(Ferdinand Mütsch) #7

Well, ok. I was confused by the server: nginx header in the responses.

(Matt Holt) #8

Caddy proxies into a Docker container that the software ships in, and inside that container, nginx serves Discourse which is in Ruby I believe.

Caddy’s auto-HTTPS just makes it so much easier to do this way.

That is strange that the server header doesn’t show Caddy too. It used to…

1 Like
(Matthew Fay) #9

Is Caddy deferring to the upstream {>server} instead of adding its own maybe?

(Matt Holt) #10

I’m not sure, I haven’t had a chance to look into it. I don’t see anywhere in the code (at quick ‘Find’ glance) where the “Server” header would be removed. It sets it one of the first things in httpserver/server.go. I’ll have to investigate further (or someone else can if they want to).

(Toby Allen) #11

I’m sure I remember a PR that changed a proxy from showing ‘caddy’ as the server to transparently showing the proxied server.

Can’t find it now though.

(Matt Holt) #12

Hmm, maybe this one?