/what/ - ...

Please use the spoiler feature/10

>>8512
https://what-ch.mooo.com/rules
hmm, all i see is a 404 page and it doesn't even have Mugi on it.

>>8513
Please use a valid ssl certificate, /what/min!

>>8514
You have to pay money for that. I use a self-signed certificate and the encryption/purpose of HTTPS works just as well with that, except common browsers will throw out a scary warning. I encourage any users of the site to be using the HTTPS version.

>>8515
Not anymore! https://letsencrypt.org/
I run one of these certs on my own server. It's not too bad to setup. They only last three months, but the client can autorenew now, so you wouldn't even have to do anything after the initial setup.

>>8515
have you looked into letsencrypt?

>>8518
>>8519
>In order to get a certificate for your website’s domain from Let’s Encrypt, you have to demonstrate control over the domain. With Let’s Encrypt, you do this using software that uses the ACME protocol, which typically runs on your web host.

Sigh…

>>8520
You're able to just upload certs as well if your host allows that but you don't have ssh access.

>>8521
I just don't want to install and learn how to use a piece of software for it, and learn more about it in general. Maybe some other day.

I did just update the site to work properly with HTTPS though, the test-php link at the top will now will redirect to http or https (depending on what you're using) rather than just hard redirect to HTTP /tp/.

/tp/ will also redirect back to HTTPS /tp/ if you make a post on it through HTTPS, rather than hard redirect back to HTTP /tp/.

>>8533
It's pretty easy to set up, honestly. I believe it even automates nearly everything if you're using apache (other webservers take a few more commands).

https://certbot.eff.org/#gentoo-apache

>>8534
/what/ runs on lighttpd

>>8538
/what/ runs on sad gay cums