supermango

enable php error logs and wp debug logs to get more details on the issue.

Have you tried changing rule #4

From R:1 to R:2–> <action type=”Rewrite” url=”{R:2}” />

This has everything to do with the way WP was initially setup during installation. If you install from site1.com and then later try to map custom-doman.com to site.com, the plug-in does not remedy that.

I agree with Ron, I don’t think there is an issue w/ the plug-in. Rather server config.

The issue that I saw on Azure (IIS) was in web.config. There was a redirect rule that was hindering the multisite admin interface.

With that said, the issue that I faced was if I initially created the WP site at: example.com

and then later tried to point another-example.com to example.com, then it would run into issues. Meaning, you can’t map the primary site using the plugin. I was only able to map secondary sites. Please correct me if there is a way to may the site WP is installed on.

That’s great. I’m facing the same issue. Do respond if you have been able to get past the issue.

Hi dpeschio – Were you able to resolve this issue?

Have you been able to resolve this issue? If so, can you please respond with the solution.

Beltran_r,

Can you please copy/paste your changes in the files? Were you able to make any more progress on this? Thanks!

Grrrr… the problem on my server was that the php files need the shebang line at the very top.

admin-ajax.php was missing this line, therefore it was resulting in an error in the ajax response. this fixed the problem for me.

i don’t think this is a normal case. you should check with your server administrator if php files need the shebang line. if you have other php scripts on your server and you’ve never had to manually add that line in, then chances are that something else is wrong.

You don’t have any links in your blogroll. If you don’t intend on having any links, you should edit the template and remove the blogroll.