Need help? Check out our Support site, then

Mapped subdomain blog has log in problems

  1. Hello,

    this post began with a problem I had and managed to solve before posting. Since the domain mapping support pages don't mention this (and I think they really should) I will post this anyway in the hope it helps people encountering the same problem.

    Situation: You have a blog succesfully mapped to a subdomain you own. (I don't know for sure it happens also with full domain mapping, but it could).

    Problem: When you go to your blog and try to log in, you are redirected to the dashboard. There, everything works fine, but when you try to actually browse your blog at your own subdomain, you mysteriously appear as logged out. Whatever you do, you can't login unless you are in the domain, and then your blog refuses to take notice.

    Cause: You have disabled third party cookies in your browser (or firewall or whatever). Thus, your log in is only valid under the domain, not your own subdomain.

    Solution: The only solution is allowing third party cookies, which I hate because then you are exposed to privacy invasion by everyone and their pets. A more reasonable solution would be to allow third-party cookies only from, if your browser supports it.

    Workaround: Have two browsers (say the one bundled with your OS and Firefox/Opera) and enable third party cookies in one of them, then use it only to browse your blog.

    As far as I know, this problem can't be solved because that's the way cookies and browsers are supposed to work, and there's only one domain actually hosting the blog and handling authentication ( to begin with. Still, disabling third party cookies is a sensible practice, so I think this caveat should be mentioned somewhere.

    Thank you.

  2. I'm not seeing this, and I have five domain mapped blogs here. Could you give us your specific URLs?

  3. Make sure your browser is set to accept cookies from third-party sites.

  4. raincoaster, thesacredpath,
    as I wrote initially I managed to solve this before posting, but since a previous search of the forums found nothing, I thought I'd leave a post describing the problem and its solution so it could be easily found by people having this same problem in the future.

    I posted it under Support as Not a problem - topic about how works, but apparently this info isn't shown. I just changed the status from Not a problem to Resolved to make sure.

    Thank you

  5. And if I had read more carefully, I would not have suggested what you had already found out.

Topic Closed

This topic has been closed to new replies.

About this Topic