The default_server setting of the listen directive should determine which certificate is sent for a request without SNI set in the handshake. Change the listen directive of the desired default:
listen 443 default_server ssl;
@Undo you can quickly check the default cert by going to the ip domain https://54.236.78.156/, and that checking what certificate is giving the problem
I'd rather not have to explain to the university how one of their now-essential web services is down for an indefinite period because I upgraded the system to support a spam detection bot...
It can be fixed without skipping security checks on my side, so I'm happy for now. I'll do the release upgrade at some point soonish so that we can actually support SNI properly
@BrockAdams I think maybe they're somehow intending to use Stack Overflow questions for some extra purpose? But it's not clear, I'll give them some time to respond first and see if they have a satisfactory explanation
After upgrading Ubuntu, I see that had to reinstall mysql because conflicts in the config file that I didn't want to take time to fix, I also need to update my tmux config file because something's changed with mouse mode
@Undo if you need the server, let me know, the only thing running on it has been moved to a different system, so it's free for boot-and-nuke and then setup for whatever Smokey needs, if needed.
@ArtOfCode While I don't have the keys, I know I can get smokey quickly up and running if its need to be (did it yesterday to implement the HB packets)
@ArtOfCode barring that, or if you guys need another failover solution for critical evils, let me know, the server'll be there if needed :)
(currently at 99.9958% uptime the past five weeks lol, I rebooted for kernel repair 5 weeks ago and only turned it off once to unstick a process that has since been destroyed)
Will do. There's always times when Smokey breaks and goes offline entirely, at which point someone just picks it up for a few hours until whoever's hosting it can fix things