Problem z Wordpressem, Not found Opcje

[Pawel.Dabrowski]

Witam.
Co moglo sie stac z moim blogiem (http://pdabrowski.art.pl)
Po kliknieciu na dana notke albo na podstrone pojawia sie not found.

Dziala jedynie zmiana na domyslny i na razie tak zostawilem.
Zalezy mi na tym by bylo tylkp %postname


DODANO 08.12.2014 12:24

Nikt nie jest w stanie pomóc?
Teraz po próbach z konfiguracją serwera pojawił się kolejny kłopot:
Mianowicie zaraz po wejściu na pdabrowski.art.pl pojawia się komunikat:



Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@pdabrowski.art.pl and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.[/php]

Ten post edytował Pawel.Dabrowski 8.12.2014, 12:24:36

[hankos0]

Witaj!
To wygląda jak błąd w pliku .htaccess
Pokaż zawartośc tego pliku.

[Pawel.Dabrowski]

Options FollowSymLinks
AllowOverride All

# BEGIN iThemes Security
# BEGIN Ban Users
SetEnvIF REMOTE_ADDR "^111\.93\.180\.66$" DenyAccess
SetEnvIF X-FORWARDED-FOR "^111\.93\.180\.66$" DenyAccess
SetEnvIF X-CLUSTER-CLIENT-IP "^111\.93\.180\.66$" DenyAccess

SetEnvIF REMOTE_ADDR "^175\.126\.62\.151$" DenyAccess
SetEnvIF X-FORWARDED-FOR "^175\.126\.62\.151$" DenyAccess
SetEnvIF X-CLUSTER-CLIENT-IP "^175\.126\.62\.151$" DenyAccess

SetEnvIF REMOTE_ADDR "^178\.208\.38\.98$" DenyAccess
SetEnvIF X-FORWARDED-FOR "^178\.208\.38\.98$" DenyAccess
SetEnvIF X-CLUSTER-CLIENT-IP "^178\.208\.38\.98$" DenyAccess

SetEnvIF REMOTE_ADDR "^211\.110\.140\.70$" DenyAccess
SetEnvIF X-FORWARDED-FOR "^211\.110\.140\.70$" DenyAccess
SetEnvIF X-CLUSTER-CLIENT-IP "^211\.110\.140\.70$" DenyAccess

SetEnvIF REMOTE_ADDR "^192\.163\.255\.108$" DenyAccess
SetEnvIF X-FORWARDED-FOR "^192\.163\.255\.108$" DenyAccess
SetEnvIF X-CLUSTER-CLIENT-IP "^192\.163\.255\.108$" DenyAccess

SetEnvIF REMOTE_ADDR "^108\.59\.12\.73$" DenyAccess
SetEnvIF X-FORWARDED-FOR "^108\.59\.12\.73$" DenyAccess
SetEnvIF X-CLUSTER-CLIENT-IP "^108\.59\.12\.73$" DenyAccess

SetEnvIF REMOTE_ADDR "^191\.241\.143\.11$" DenyAccess
SetEnvIF X-FORWARDED-FOR "^191\.241\.143\.11$" DenyAccess
SetEnvIF X-CLUSTER-CLIENT-IP "^191\.241\.143\.11$" DenyAccess

SetEnvIF REMOTE_ADDR "^188\.214\.29\.99$" DenyAccess
SetEnvIF X-FORWARDED-FOR "^188\.214\.29\.99$" DenyAccess
SetEnvIF X-CLUSTER-CLIENT-IP "^188\.214\.29\.99$" DenyAccess

order allow,deny
deny from env=DenyAccess
deny from 111.93.180.66
deny from 175.126.62.151
deny from 178.208.38.98
deny from 211.110.140.70
deny from 192.163.255.108
deny from 108.59.12.73
deny from 191.241.143.11
deny from 188.214.29.99
allow from all

# END Ban Users
# END iThemes Security
# Disabling cache management
# that could cause problems with DAV requests
# Useful only for Apache servers, with AllowOverride All
# (ie, .htaccess files enabled)

# Allow HTTP headers with Apache/FastCGI
# See http://code.google.com/p/sabredav/wiki/Aut...che_+_(Fast)CGI

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]
</IfModule>

<IfModule mod_expires.c>
ExpiresActive Off
</IfModule>

# BEGIN WordPress

# END WordPress

[hankos0]

Jeśli możesz zalogować się do admina to wyłącz wtyczkę iThemes Security
w .htaccess wstaw standard wordpressa i sprawdź efekt

[PHP] pobierz, plaintext 
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
[PHP] pobierz, plaintext