New install shows "Oops something went wrong" on any action

User20

I just installed fresh Flarum on a subdomain and wanted to set it up. I can browse around, opet profile/settings/admin but I cannot do anything.

The issue

I keep getting the "Oops! Something went wrong. Please reload the page and try again." error message whenever I try to post, save settings, edit anything, open notifications, etc. I tried to check if its browser-related but I can't even log in because I get the same message when I try to log in from somewhere else.

What I tried

I turned on debugging mode but the "DEBUG" button doesn't show. Not sure why.
I followed all of the setup from the intall instructions, besides URL Rewriting part. I contacted my hosting support about this and they said: "We can confirm that mod_rewrite is enabled on all our servers by default. However, the directive 'AllowOverride All' is not allowed on our servers due to security reasons."

What might be the issue

In my browser console, I see that whenever I do any of the actions above I get an error that the relevant information (login, notifications, etc) are being loaded over http instead of https and the request is therefore blocked.

I contacted hosting support about this but they told me this is an issue due to how the app was built. I have a Wildcard SSL with HTTPS enforcing so they said this is due to http being hardcoded/forced somewhere in Flarum. This sounded strange to me so I escalated the issue to 2nd level support, but I'm still waiting to hear back from them.

I'm out of ideas of what to try, so I would please appreciate some guidance. Thank you!

jordanjay29

User20 Can you check if the URL field is set correctly in your config.php? Make sure it is exactly the same URL you are using to access/login/post/edit/etc, minus the trailing slash. So it should look like https://flarum.mysite.com for example.

User20 I turned on debugging mode but the "DEBUG" button doesn't show. Not sure why.

This is known and reported.

User20 "...However, the directive 'AllowOverride All' is not allowed on our servers due to security reasons."

It's possible this will have an effect, but let's make sure other settings are valid first. But keep in mind that this is one of the reasons Flarum on shared hosting is so tricky.

User20

jordanjay29 YES! That fixed it right away.

The issue was that the "http" link was in the config.php file... fixed it to "https" and now everything works perfectly. Can't believe it was such a miniscule error I've been busting my head over for hours.

Thank you for your help and the fast response, excited to get started with Flarum!

Broxi

I've installed a fresh Flarum today as well. Because of I was not able to open my URL using the host-part only (http:// xzy.com) without the index.php, I started the Installation by adding the index.php in the Browser. The Flarum-Install seems to get the full URL including the index.php as Base-URL and therefore saved that in the config.php.

jordanjay29

Broxi Yes, the OP's situation can occur, however, if an SSL certificate is added/updated later (which isn't uncommon for subdomains, since wildcards are not usually accepted in free SSL certs like Let's Encrypt) or if you simply forget to navigate to the https url, unless your server has a redirect most browsers will default to http when omitting the protocol.

User20

jordanjay29 Actually, I do use a Let's Encrypt Wildacard SSL that I enabled before installing Flarum. But for some reason, I had to update it after installation because Flarum was using http and the https version just redirected me to the main domain.

I fixed this with the hosting support and HTTPS enforcing though but, in hindsight, this is probably where the issue originated from, as the http in the installation was a remnant of this.

ahrasis

I modified my config.php and am using this in it so it could work for both with and without ssl.

'url' => (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] === 'on' || $_SERVER['HTTPS'] === 1 || $_SERVER['HTTPS'] === 443) ? 'https://' : 'http://') . 'my.domain.tld',

By the way I am not encouraging anybody not to use ssl though, as using ssl is easy (and free with Let's Encrypt) and it is the preferred way these days.

luceos

ahrasis the best solution is to forward http to https requests inside your web server. Otherwise on http users might unsafely try to log in or register, making the request vulnerable to man in the middle attacks.

ahrasis

ahrasis I modified my config.php and am using this in it so it could work for both with and without ssl.

The use is not for redirect but rather for both http and https.

ahrasis By the way I am not encouraging anybody not to use ssl though, as using ssl is easy (and free with Let's Encrypt) and it is the preferred way these days.

And I did not post to encourage not to use ssl. 😉