Running Flarum in subdomain.

gcgc

I have installed Flarum on my VPS, and have set up my domain name resolution so that abc.domain.com is resolved to that VPS's IP. The result is when the browser navigates to abc.domain.com, the forum shows up. With everything else running ok, I am having this issue: each time I log out (click the Log Out link on the profile dropdown), the browser redirects to wildcard.domain.com, and Flarum stops working.

This seems to be related to my Apache VirtualHost settings. My settings are:
<VirtualHost :443>
SSLProxyEngine on
ServerAdmin admin@domain.com
ServerName wildcard.domain.com
ServerAlias .domain.com
UseCanonicalName on

It seems that the ServerName in the settings (wildcard.domain.com) is used as redirect url. My guess is that somewhere in Flarum $_SERVER['SERVER_NAME'] is returned.

How can I make it always redirect to abc.domain.com when logging out?

gcgc

Anyone have an idea on this?

I've looked into LogOutController.php, and the $url returned in handler method is correct (that is, abc.domain.com). So somehow/somewhere the logout process redirects to wildcard.domain.com, and I can't figure out.

Any suggestion would be appreciated!

Thanks!

luceos

gcgc so the actual domain returned is wildcard.domain.com or does it have a specific value? What value do you have configured in your config.php under url?

gcgc

luceos, thanks for getting back to me.

The url value in config.php is: 'https://abc.domain.com/forum'.

The browser is supposed to redirect to abc.domain.com, but instead it redirects to 'wildcard.domain.com'. I also tried to change ServerName in Apache VirtualHost settings to something like wc.domain.com, then logout redirected to wc.domain.com. Therefore it does seem that Apache's ServerName is returned for redirection while logging out, and the subdomain is messed up.

luceos

gcgc flarum does nothing with redirection except for the value in your config.php. If there is some other redirection happening it is caused by either from a wrong .htaccess or vhost config. I'd open the network tab in the developer console and enable "preserve log" then see what process is executing the redirect, this can be seen from the Response Headers.

gcgc

luceos, I did what you said. It seems that the redirection might happen in Apache. And here is the latest.

If I set the url value to: 'https://abc.domain.com/support/forum', then perform the following 3 steps:
1 browse to 'https://abc.domain.com/support/forum/';
2 log in;
3 log out;
now the browser is redirected to: 'https://wildcard.domain.com/support/forum/'; this is not correct.

If I set the url value to: 'https://abc.domain.com/support/forum/' (note the trailing slash), then perform the same 3 steps as above. Now the browser is redirected to: 'https://abc.domain.com/support/forum//'. Although the forum shows up okay, the trailing double slashes are always present.

gcgc

Also, whenever https://abc.domain.com/support/forum/ is accessed, an extra slash is always appended to the url, after page is fully loaded.

gcgc

Is this extra slash caused by .htaccess or in Flarum?

I am not seeing any rule in mod_rewrite could cause this. I am simply using .htaccess under Flarum installation's root directory.