Backbite

It has to be something in the Google cloud platform. When it comes time to wipe the server, I'll try it on the new distro.

It seems to send a new cookie every time I attempt to login. Not sure if this is intended behavior? The working server doesn't seem to do this...

I think this is what you're talking about. Hopefully the link works.

I have, it works perfectly fine on a full fat Debian 8 installation. I used firefox's developer tools to check and verify that the session and cookies were being set the exact same way on both servers. (The working and non-working server.) And line 239 of Web.cs in the source is where it should be passed off. I agree, it's supposed to work without external dependencies. The only possibility I can think of right now is a very scenario-specific Mono bug - possibly related to the core OS/kernel (???) Edit: I've also checked with browsers outside my internal network, and from completely different computers.

I replicated the issue with a fresh Google compute VM. Their Debian 8 image is so stripped down and lightweight that it seems to be missing something. Everything else about the server runs great. Once a new release comes out or people get bored with the server, I'll try again on Debian 9.

It seems to be only broken in my particular setup using google compute VMs. I created a test box using a hyper-v VM, A15.2 works fine, and when I upgrade it to A16 it still works. I'll have to compare all the installed packages.

Steam OpenID not passing Hello everyone, I've installed a server, A16, and the server fixes on Debian 8. Permissions and everything work. The console shows the OpenID getting passed "2017-06-18T10:40:07 99.985 INF Steam OpenID login from 71.xx.xx.xx:55594 with ID 76561197986258927, permission level 0" But the web page on 8082 returns "Not logged in." after the OpenID transaction. Anyone else experienced this? Edit: I've noticed the error INF Steam certificate error: RemoteCertificateChainErrors, which appears to be coming from the steamcommunity.com response. Is there a certificate I need to update on Debian to make it work? the ca-certificates package is already up to date.