Wordpress HTTPS doesn't work out of the box on Online.net Shared Hosting


I’m using Shared Hosting, with https enabled on it.
When I place Wordpress php files into the site, http displays things fine, while https is displaying incomplete/buggy webpage (no CSS, no pictures)

Even if I do the complete initialization, http is working fine at the end, while https is buggy.

Modifying “wp_options” -> “siteurl” and “home” in order to write https instead of http, does nothing helpful : the wp-admin isn’t available anymore (redirection loop). Same problem when adding to wp-config.php :

//Use HTTPS for WordPress
define('FORCE_SSL_ADMIN', true);

I saw on the documentation that a plugin can be used (Really Simple SSL). It solves the problem, but it’s not fine. I don’t want to place an unofficial plugin containing thousands of workaround code lines to simply enable something simple that should have been working out of the box.

When I put a wordpress into an Apache2 / Linux server with https enabled, Wordpress on https works fine out of the box without any thing to do or any unofficial crap to install.

If somebody knows what is malfunctioning with the default Wordpress installation, HTTPS, and Online.net Shared Hosting, I’m interested !

Thank you in advance


I guess there is something wrong here, already :

How to repair that ? As the server says it’s on port 80 (and may be http instead of https), Wordpress is malfunctioning (redirecting to https despite the fact it’s already into https, again and again, and probably lots of others things like wrong links.


Same issue here, without any HTTPS activated, what’s the problem?


Hi, by talking with support about this problem, it seems that this is because of the way their servers are communicating with each others.

When you are connected using HTTPS, you are actually connected to a “front server” which isn’t the server that generates the page : the link between the 2 server does not seems to use HTTPS, so the server that generates the page is still using HTTP. A loop redirecting to HTTPS when the server is seeing you as HTTP will then be infinite, blocking (this is what happen to wp-admin)

For the broken views, I’m not sure about which mechanism is causing it.

They know that it’s a little bit bothering but I don’t know if they will fix it or not, and if so, how many time should be expected before this is solved

1 Like