Dashboard unavailble from the subsite (multisite)

I’m on a windows server and .htaccess is not accepted, iirf.ini however is.

What kind of Windows server? Is it running apache? What about IIS? What versions of those?

Sohosted uses exclusively windows server 2003, in combination with IIS6 (internet information services 6)

so it reads on their site.
https://www.sohosted.com/helpdesk/faq/vraag=85/op-welk-platform-host-sohosted

I hope this helps ?

URL’s rewrite is also possible, but not with htacces, but iirf.ini

That does a little.

Basically the iirf.ini works the same as .htaccess.

Okay, can you check if you have an ISAPI rewrite filter in the web server? You may need to ask sohosted.

ok, email sent. it probably will be tomorrow when I get a reply.

They do support rewrite, but I’m afraid that’s getting a bit too technical for me at the moment…

some info here:
https://www.sohosted.com/helpdesk/faq/vraag=129/kan-ik-urls-rewriten-sefseopermalinkshtaccess

Google Translate…

If the loaded rules do not work there is a chance that the rules should be adjusted. A situation that we often see going wrong is that it is necessary to place slashes at the beginning of a rewrite rule. A rule like: RewriteRule ^(.*)$ index.php? rewrite = $ 1 should then be adjusted to: RewriteRule ^ / (.*)$ / index.php? rewrite = $ 1

That’s possibly what’s wrong, but between having to rely on Google to translate Dutch and knowing nothing of this file, I’m iffy about suggesting specific changes.

that’s a correct translation, I’ll go ahead and try this, in the meantime I’m awaiting an answer to my email. Will keep you posted as soon as I can.

just to be clear, is this a correct replacement then ?
edit: it is not since it is still not working, probably missing something.

# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^/index\.php$ - [L]

# uploaded files
RewriteRule ^/([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^/([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^/ - [L]
RewriteRule  ^/[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
RewriteRule  ^/[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
# END WordPress

Just a silly question probably, but there are no folders as the login page suggests.
/login/
/login/diary
/login/newz and so on…

I don’t need to make those directories, right ?
I have a blogs.dir in the wp-content (also emtpy) but if I understood it right that should be the case too.

they support ASAPI, no word of them yet officially but found out googling around that they do have it on their servers.

I don’t need to make those directories, right ?

Correct. DO NOT make those directories. They’re virtual.

Hrm… That’s the .htaccess I would have tried.

This bit kind of confuses me.

# WordPress
#
# Uncomment the following rewrite rules. For URL rewriting (Permalinks) activated in WordPress, you can
# click to Permalinks -> Custom Permalinks Structure "click and as /% postname% / enter.
# The rules assume that WordPress is in the folder wordpress.
# if not the case, remove the value "wordpress/" .
#
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule /wordpress/. /wordpress/index.php [L,QSA]

Okay… I re-read this older post https://www.ads-software.com/support/topic/themes-applied-no-images-appear-for-multisite-sub-directorys-sites?replies=7

It looks like he’s using the original .htaccess as his ini file, but added

# StatusUrl /iirfStatus
StatusInquiry ON
RewriteLog C:\windows\system32\LogFiles\iirf\iirf
RewriteLogLevel 1
RewriteRule /eurl\.axd/ - [L]

to the top?

I now have

# StatusUrl /iirfStatus
StatusInquiry ON
RewriteLog C:\windows\system32\LogFiles\iirf\iirf
RewriteLogLevel 1
RewriteRule /eurl\.axd/ - [L]

# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^/index\.php$ - [L]

# uploaded files
RewriteRule ^/([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^/([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^/ - [L]
RewriteRule  ^/[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
RewriteRule  ^/[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
# END WordPress

and it is still not working…

sigh…

I’m gonna give up any minute now I think…

The support at sohosted fixed it for me, it was down to slashes and spaces.

Here’s the iirf.ini for anyone battling the same issue.

# BEGIN WordPress
RewriteEngine On
RewriteBase /login/
RewriteRule ^ index\.php$ - [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule  ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
RewriteRule  ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
# END WordPress

also, this file is in the wwwroot folder, so one folder up from where my install is located, in the folder /login/

Whew! I’m glad it was just semantics! I’ve tagged this with iis6, iirf.ini and sohosted, so hopefully it’ll show up on searches next time!