@phenomlab It seems that I may have it fixed.

As I could log in using the old domain, I took out the Session cookie domain setting in the admin section. Then log in using the new domain started to work. Actually, both domains work now.

Earlier I changed that value from the old domain name to the new domain. But that didn't work. Then I saw a tip under the setting box that reads "Leave blank for default". So I made it blank. I assume that the default is the host name in the HTTP request?

I want to think you for your writing. That lead me to the right direction.

Thank you all for the responses. This is a wonderful community - Makes me feel much better exploring this new thing.

Wishing you all the best!

@julian : That did it! Thank you much.

Yes. I use nginx -- I should have mentioned that in the original post.

That option was set to proxy_set_header X-Forwarded-Proto http;

Had a bit of time to try to debug this. I started the up NodeBB in VS Code in a debug session and set break points in Google.init() and Google.getStrategy() functions. The debugger stopped in both. However, in Google.getStrategy() I found both Google.settings.id and Google.settings.secret undefined.

It seems that the async call to meta.settings.get('sso-google', ...) finished after the call to Google.getStrategy(), so even though the the Google ID and secret are loaded fine, they are too late.

I am running NodeBB with a PostgreSQL backend for that matter.

@baris Thank you for the quick fix! It works now.