"Something went wrong [...]" error after switching to https.

T_Medias

Ok, here's what I did to obtain this error :
1) Made my website work well with http
2) Inserted "flexible" https rules on my cloudflare config for the subdomain where my forum is installed
3) Changed the config file to match the https url
4) Cleared all caches (flarum, cloudflare, browser)

Since that, I have the error "Something went wrong while trying to load the full version of this site. Try hard-refreshing this page to fix the error".

When I activate debug mode, I don't see any messages, even after clearing caches again. I checked logs and I saw some errors, but can't understand what they are or if they are related to the issue :
#25 /home/dasiwuididdd/data/www/vendor/flarum/core/src/Http/Middleware/HandleErrors.php(57): Laminas\Stratigility\Next->handle(Object(Laminas\Diactoros\ServerRequest))
#26 /home/dasiwuididdd/data/www/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Http\Middleware\HandleErrors->process(Object(Laminas\Diactoros\ServerRequest), Object(Laminas\Stratigility\Next))

Thank you in advance for your help.

askvortsov

T_Medias the error message you're seeing on the site seems like a frontend error. Check the dev tools (inspect element) log for any error messages

010101

T_Medias Just a guess. Whatever way you can, make sure https is forced. This may not be your issue, but I had weird problems after a fresh install one time until I added a redirect rule to my .htaccess file saying to always ensure any http traffic redirects to https.

T_Medias

askvortsov Thanks for your reply.

The javascript console says it fails to load "../assets/forum-68b8e969.js" and "../assets/forum-en-56f96d01.js". Is it cache related ? How can I clear it in order to solve it ? Tried everything...

askvortsov

Are you sure that cloudflare is serving your js and css properly?

T_Medias

askvortsov

Hmm... Maybe I should deactivate rocket loader and css minification ? But the thing is it worked well before switching to https...

EDIT : I deactivated rocket loader and js/css minification. Didn't solve the problem.

The browser console shows the website is trying to load a lot of missing assets (js and css). I think it tries to load old cached assets. How can I clean the assets call ?

T_Medias

askvortsov Any idea ? Do you know why flarum is trying to serve unexisting assets files ?

[deleted]

T_Medias have you cleared the cloudflare cache, and also your local browser cache ?

T_Medias

[deleted] Yes I did.

T_Medias

010101 Also tried that, didn't solve. :-/

clarkwinkelmann

T_Medias what's the fully qualified URL to the inexisting files? If it's the URL without https despite config.php being updated, there's something still cached by a proxy somewhere.

If it's an https URL but just a file that indeed doesn't exist, try clearing Flarum cache once more.

T_Medias

clarkwinkelmann Hello.

Now the files it tries to get are present into the assets folder, but the browser still can't get it (HTTP/1.1 404 Not Found).

I cleared flarum cache, cloudflare cache and browser cache... Still not working...

[deleted]

T_Medias can you disable cloudflare then try again ?

T_Medias

[deleted] Can't disable it unfortunately because cloudflare own the https certificate.

T_Medias

I just did a fresh install. Always the same error. Flarum is unable to get flarum js and css files..

askvortsov

If the files are there, you should look into potential errors in your web server (nginx / apache) configuration

clarkwinkelmann

You can also "disable" Cloudflare by putting it in development mode. This will temporarily disable all Cloudflare cache-related features for troubleshooting.

T_Medias

Ok guys, this is how I solved the issue : after making the forum work with a private ssl certificate installed on my server (using cloudflare on dns only), I tried some other things like deactivating only the SSL on cloudflare (with a page rule), but didn't work.

After that, I simply changed the page rule to "SSL : strict" and reactivated cloudflare proxy. Now, the forum works pretty well on https.

Thanks a lot for your help anyway :-).