RedChili

I finally figured out what was wrong. When I tried to map the domains, I used the wrong site ID number in Network Admin – Settings – Domain. It was a really stupid mistake.

I’m not sure what you mean with “make host entry.”

The instructions you’re talking about for admin dashboard is what doesn’t work for the new domains. See the images that I posted on top. The whole point of this thread is that I don’t understand why it doesn’t work. It should work in WP 5.3.2.

My memory is a bit obscured, but as far as I can remember, I think that when I installed WordPress with my current provider, I couldn’t make the native domain mapping to work. I therefore installed the WordPress MU Domain Mapping plugin. So, that’s how I mapped my old domains. But that plugin doesn’t offer support for the current version of WordPress, and that’s why I can’t map my new domains. So in order for me to ble able to map new domains, I’ll have to either install another plugin, or to make the native mapping to work, something which it doesn’t do at the moment. Any advice?

The main domain and all the other domains are working and have worked since I installed them. It’s just the two new domains that I added this week that for some reason don’t map automatically.

I can log in as admin on Cpanel, WordPress, FTP for both the main domain and all the old domains that have been there.

When you’re asking about these files, do you mean the main domain? In that case, the answer is: no wpdemos.php, yes index.php, yes htaccess. The following directories exist: .well-known, cgi-bin, wp-admin, wp-content, wp-includes. The following files are there: htaccess, default.htm, index.php, license.txt, php_errorlog, php_mail.log, readme.html, wp-activate.php, wp-blog-header.php, wp-comments-post.php, wp-config-sample.php, wp-config.php, wp-cron.php, wp-links-opml.php, wp-load.php, wp-login.php, wp-mail.php, wp-settings.php, wp-signup.php, wp-trackback.php, xmlrpc.php.

I’m not sure about what you mean by “did you remember to point the addon domains to the WordPress directory under public.” All my domains, both the old ones that work and the new ones that don’t work, are routed via DNS from my registrar to my host.

Thanks for the answer. I’ve read that document and it didn’t help me anything. The thing that’s really puzzling is that all the domains that I mapped a couple of years ago worked perfectly, but those that I’m trying to map now don’t work at all. And I’m doing everything in the same way.

When I try to access one of the new domain names, I get the following error message:

500 – Internal Server Error
This is a temporary server error.
Please try to reload the webpage later.

If you are the webmaster of this site please log in to Cpanel and check the Error Logs. You will find the exact reason for this error there.

Common reasons for this error are:

Incorrect file/directory permissions: Above 755.
In order files to be processed by the webserver, their permissions have to be equal or below 755. You can update file permissions with a FTP client or through cPanel’s File Manager.

Incorrect Apache directives inside .htaccess file.

Make sure you have not specified unsupported directives inside the local .htaccess file. Such include PHP settings and Apache module settings.

The permission is 755. The htaccess works with all the other domains mapped through the same multisite. The error log I get is:

script not found or unable to stat: /home/myaccount/public_html/wpdemos.php

I forgot to add that I have WP 5.3.2.

I’m struggling with a similar situation as you, although I haven’t come as far as you do yet.

I believe that what you need for your site is an SSL which supports subdomains (i.e. a “wildcard domain SSL”).

But I have a question for you: When you try to access the back end of your site, i.e. staffblog.ucc.edu.gh/wp-login.php, does the server also try to force https for that page, or is it only the front end seen by visitors?

I’m using a plugin which may be of help to you. It’s the “MultilingualPress”. The purpose is that you can write posts in several languages in just one admin page.

So, I have three sites running, english.blog.com, norwegian.blog.com and swedish.blog.com. They are connected through the plugin. So, whenever I go to “New post” on any one of those sites, I get fields for translation into the other languages as well (if I want to use them, I can still write a post in just one language if I want to) .

I guess that you could use such a plugin to accomplish some of the things you want.

Thanks! That’s exactly the plugin I’m using.

However, when I uncheck that box, I’m logged out and have to log in again separately when I want to switch between the different sites on my network.

Additional question: Let’s say that I’m running a multisite with domain mapping via a plugin, which means that I access the back end of WP through https://mappeddomain1.primary.com/wp-login.php, but the front end is accessible via https://mappeddomain1.com.

I then install an SSL which supports multiple domains, but not wildcard (subdomains), and I configure WP to use SSL for the entire site.

Will that create problems when I try to access the back end through https://mappeddomain1.primary.com/wp-login.php? Will WP try to redirect me to the non-existent wildcard certificate on https://mappeddomain1.primary.com/wp-login.php?

OK, thanks, I’ll review my options.

OK, thanks!

My host will anyway charge me for installing SSLs for all additional domains.

Well, actually, in the end I gave up. I thought that I had solved the problem several times, but for some unexplicable reason, the problem surfaced again after I had logged out and in a couple of times. Really strange. I tried all possibilities, including the one you mention.

So, in the end I gave up and instead installed the plugin for domain mapping. Now it’s working perfectly. But no matter how hard I tried, I couldn’t get the native domain mapping feature to work correctly.

I finally solved my problem!

In config, I added the following line:
define(‘COOKIE_DOMAIN’, ‘.mydomain.com’);

(Important: Note dot in front of mydomain.)

That solved all my problems.