MyBB Community Forums

I think the answer to this question has been right in front of me, but I just can't find it.

I recently upgraded from 1.2 to 1.4. Everything is working fine except:

I can only log in to my ACP using http. If I login using https, I get a screen, but when I try to go to the next screen, it asks me to login again. When I do, I'm at the next screen... and so on. It acts like it doesn't know where the cookies are. But only when I login using https.

Note that I'm using the ssl cert of the parent domain for https access. So the sitename/path is different. But it was different when I was running version 1.2 as well, and I didn't have this problem.

site url: www.fuel-saver.org/
https path: www.fuelsaver-mpg.com/fuel-saver/

I think there's a setting somewhere that I'm missing, so that the https site name and cookie path are known. But I haven't found where to do this.

I'm pretty sure I'm missing something real easy to find somewhere, but I have not been able to find it.

Thanks.

Hasn't this thread been made once already??

I think last time I said that having 2 different URLs, in the way you have, is a problem... both the cookie domain and path are different.

Unless I'm misunderstanding the problem here.

I think I saw that post. I know I posted on another thread some weeks ago when this first came up. But I think there's a mis-communication of some sort.

Before upgrading, I didn't have any trouble with this. I was using a shared ssl cert on my old host. The urls to my forum root directory were as follows:

site: www.fuel-saver.org/Forum
https: www.link-ssl.com/fuel-saver/Forum

This worked fine, and I didn't have this same problem. I was able to log in to the ACP using https, with no problems.

Now the topography is slightly changed, but it's still the same basic setup, and using a shared ssl cert, but I'm now using the root directory:

site: www.fuel-saver.org/
https: https://www.fuelsaver-mpg.com/fuel-saver/

I think I must not have made the problem clear earlier, because I'm sure that MyBB is able to use a shared ssl for https access like this. It was working for me under version 1.2. I moved to the new site and topography before upgrading, and it still worked. Then when I upgraded to version 1.4, I started having trouble with it.

Is this what you already understood?

I think I've made this all too complicated.

Prior to my upgrade to 1.4, I was able to access my ACP using a shared ssl certificate. The https url had a different host name than my forum host name. After the upgrade, I've not been able to do it any more.

Isn't there a standard handling for using a shared ssl, so the ACP can be accessed on a secure link?

---

I've had a PM with Matt about this, and I'm bringing the topic back here to the forum, so all can see the result:

Quote:Hey,
The only thing that doesn't look right to be is the two different URLs. But if you're sure that isn't the problem, I don't know what else it could be, sorry.

I think that I must have been using the MyBB url in the https requests, and then having permanently accepted the ssl cert from a different site, was able to use it transparently after that. It may well be my new hosting environment. When I try to use https with my MyBB url, I get redirected to the home page of the parent domain. It even still shows the myBB url.

Anyway, I've finally gotten it through my head that MyBB won't work with the different urls.

I would like to make a feature request, though: And that's to allow the ACP to have a separate domain name so that shared ssls can be used to access the ACP securely.