sailorrr
About
- Username
- sailorrr
- Joined
- Visits
- 52
- Last Active
- Roles
- Member
Comments
-
Yes, I also have this problem. Overall it seems like this is very raw panel and it's not ready for production. It works somehow, but not feeling like a reliable tool. Sad I already used it for my customers sites and there are lots of sites. Hard to …
-
Oh, things got weirder: RewriteCond %{REMOTE_ADDR} !^127\.0\.0\.1 RewriteCond %{REQUEST_URI} wp-cron.php|xmlrpc.php [NC] RewriteRule .* - [F,L] xmlrpc.php - shows 403 wp-cron.php - white page, as usual
-
No, no, I don't want to offend you in any way! Instead I'm very grateful to you for your help. I just meant that things like this one: https://httpd.apache.org/docs/ Is a kind of hieroglyphs for me.
-
Ok, got it. Thanks you.
-
Ok, you tired of me )) I will try to recognize these admin's hieroglyphs :) Thanks for your help!
-
is {SERVER_ADDR} possible here instead of {REMOTE_ADDR} ?
-
Please can you show an example? And thanks for your time and patience :)
-
Yes, yes. Exactly like this: go to server conf -> log set Log Level to DEBUG set Debug Level to HIGH
-
and this moment is confusing: RewriteCond %{SERVER_ADDR} !^123\.123\.123\.123 RewriteRule wp-cron.php$ - [F,L] Why it gives 403 if I request /wp-cron.php?doing_cron But it doesn't restrict access if I request just /wp-cron.php
-
Yes, did it, and still have only Info/Notice records without a single rewrite record...
-
Yes, did it exactly as you said. No such (REWRITE) records...
-
Some news: Domain.com/wp-cron.php?doing_wp_cron - gives 403, but just a Domain.com/wp-cron.php - gives white page reloading... And for some reason I have zero [REWRITE] INFO in my logs My rules looks like: RewriteCond %{SERVER_ADDR} !^123\.…
-
Just one moment - when I add wp-cron.php to this sentention: RewriteCond %{REQUEST_URI} xmlrpc.php|wp-cron.php [NC] RewriteRule .* - [F,L] It works. But doesn't works in: RewriteRule wp-cron.php$ - [F,L]
-
Debug log in OLS panel or somewhere in Cyberpanel?
-
So, I want to block any external access to Domain.com/wp-cron.php But to allow when server's cron calling to Domain.com/wp-cron.php?doing_cron...... and yes I access it by "wp-cron.php" only
-
Initially I placed this at the bottom, but now just moved it at the top. No difference. I'm editing Rewrite Rules in Cyberpanel, so it should automatically restart OLS when Rewrite Rules changed isn't it? And also I pressed Reboot Litesspeed button …
-
Just: RewriteRule wp-cron.php$ - [F,L] Doesn't work as well... Still loads white page instead of 403 While this: RewriteCond %{REQUEST_URI} error_log|wp-config-sample.php|readme.html|readme.txt|license.txt|wp-trackback.php|wp-config.php…
-
# Allow only server IP to run wp-cron.php and deny the rest of the world RewriteCond %{REMOTE_ADDR} !^123\.123\.123\.123 RewriteRule wp-cron.php$ - [F,L] This doesn't work, can you give me the right direction please? I think it would be nice …
-
Yes, I found this, thanks. But when I tried to use context for that - it doesn't works for some reason. Will appreciate any advice or direction.
-
I think he mean "how to disable on server level" but not in htaccess
-
Also interested.
-
Yes, I confirm - package limits doesn't work at all. @usmannasir @CyberPanel @whattheserver
-
@whattheserver good news, thanks! :)
-
But may I ask: what the reason of doing this (OpenLiteSpeed as Reverse Proxy server)?
-
Also you can use 2FA
-
Hi @bozden Did you solve this issue? I just got similar problem.
-
Hi, I did nothing just woke up today and get 500 error, when I turned on debug I get cyberpanel 1040, 'Too many connections'. What does it mean and does anyone resolved this?
