Search results

Yep, maybe it was a short interruption, I also have no problems reaching the site.

That was the one I was talking about when I said "something similar for apache". :)

Maybe for others. I don't use nGinx. Seen something similar for apache which also required customisation. It's working now and this is easier customisation for me.:)

I've read that, but that's exactly what I stated that it's always username info and some long password. No further explanation. So in fact: a.) it's always username info and some password b.) there is no explanation at all about if it can be changed or editted or not c.) Added to confustion is...

OMG that looks unclear "onoverzichtelijk" in Evo skin... ieks. In enhanced it's a straight view. Anyway, I've never seen the WHAT on reseller level. That's always been only on admin and user level, I wonder why. It would be good if that would finally be added to resellers too, like indeed also...

YES!!! That looks like the solution, thank you very much!! 47.128.110.22 - - [15/Aug/2025:18:53:56 +0200] "GET /robots.txt HTTP/1.1" 403 3044 "-" "Mozilla/5.0 (Linux; Android 5.0) AppleWebKit/537.36 (KHTML, like Gecko) Mobile Safari/537.36 (compatible; Bytespider; [email protected])"

There are 2 different things. a.) When using the "require all granted" option, then it overrules .htpasswd files for some reason. b.) When using the rewrite option, then it overrules the rewrite for (for example) Xenforo in .htaccess causing problems. You just suggested the one I wanted to try...

But that still contain the security risk that when using that one, then .htaccess files with .htpasswd do not ask for password anymore like reported in post #37. Unfortunately post #40 has the same issue. The result shows that the httpd-includes.conf is not -adding- things but also -overruling-...

Yes but you have to be very sure that all in there are bad. Lot of ASN's have a lot of bad users, but also contain various valid ones. So for example we didn't get any license mails anymore from some software company because of such netblock. I'm not specifically against netblocksBut because...

Oh that's not great. Because on all servers it's username info and some long password. Not a great idea if the content can't be changed to something else. It also gets re-created when doing the rewrite_confs command. In that case it seems best to me to keep using the old method with the...

Thank you! Both in the /etc/httpd/conf/extra/httpd-includes.conf and giving 403 and not 301?

Ah oke so I don't need to put the Virtualhost things in there myself? Because that was my concerning part. I'm not familiar with that. @Hostmavi I will try that one later on too. Yesterday I tried one with <Location / > and then I got an error notices that this was not allowed or something...

Nowadays a file called /etc/httpd/conf/extra/httpd-info.conf.secret is present. This contains some pre-generated username and password which is commented out. Uncommenting and using that name (info) and password is not working. I tried creating a password and username the same as I do for...

Looks like it. I tested with the empty new subdomain. And when accessing via http I got the 301 in the log. When using directly with https then I got a 200. But seems we discovered with Hostmavi that the complete httpd-includes.conf isn't doing anything for blocking at all. Also used the...

Hello Hostmavi. 1.) Exactly, I tried everything and nothing blocks, the only thing blocking is if I put rules (like in post #39) in the .htaccess. But that's not server wide. But thank you for confirming that they don't work for you either. I was already thinking I was going crazy. 2.) Thank...

Ahaaa.... oke that was where I was wrong. That makes sense and explains my confusion. Thank you!

I don't know how.

I might want to try this. But how should this be done in virtualhost or the Directory thing so it's server wide?

In Evo that links to the users password section if I'm correct, so that would be both DA & FTP.

Well... it's not the .htaccess even without .htaccess they still are not blocked. Only on this server it seems. Only 301's. On multiple domains. They have not visited the subdomain yet. I'm just wondering if the httpd-includes.conf will not just only give a 301. When testing on the other server...