Member Avatar for Joe2

I have just tried to access http://blog.seorevolution.com/2013/01/24/5133/ and get the following:

Forbidden

You don't have permission to access /2013/01/24/5133/ on this server.

Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.7a mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_perl/2.0.5 Perl/v5.8.8 Server at blog.seorevolution.com Port 80

I haven’t a clue what this means.

Can anyone help please?

  • 4 Contributors
  • 5 Replies
  • 234 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by BigPaw

Dani AI

Generated

Because and report the page loads for them while cannot, this looks like a problem local to the requester (network, DNS, host file, or IP-based blocking) or a gated resource rather than a global server failure. Quick checks a visitor can do first: open the URL from a different network (phone hotspot), use a private/incognito window, clear browser cache, temporarily disable VPN/proxy, and flush DNS (Windows: ipconfig /flushdns). Also inspect the hosts file (C:\Windows\System32\drivers\etc\hosts or /etc/hosts) for stray entries that redirect the domain.

To gather useful diagnostic data, fetch only headers from the URL so you can see the exact HTTP status and any blocking headers. Replace the example URL with the actual one from the post:

curl -I -L "http://example.com/path"

Look for a 403 in the status line, any Location redirect, or custom headers like X-Blocked-By. If you see 403 only from your IP but others get 200, try asking someone else to paste their curl -I output or use an online HTTP header checker.

If you control the site, check server-side causes: .htaccess or vhost access rules, missing DirectoryIndex, file/directory permissions/ownership, mod_security or firewall rules, or SELinux context. Typical quick fixes (example user/group may differ):

find /var/www/site -type d -exec chmod 755 {} +
find /var/www/site -type f -exec chmod 644 {} +
chown -R www-data:www-data /var/www/site
tail -n 200 /var/log/apache2/error.log

Access control syntax differs by Apache version (Apache 2.4 uses Require all granted; older 2.2 uses Order/Allow), so check which applies before changing config. If you are not the site owner, collect the exact timestamp, the full response headers (from curl), and your public IP, then contact the site administrator — those three items are what admins need to find the corresponding server log entries.

Recommended Answers

All 5 Replies

Member Avatar for JorgeM

The page comes up fine for me. Are you still getting this error?

Member Avatar for BigPaw

Did you access it from a link using a Google search? It maybe that you have clicked on a Google link that leads to the purchase page of the site for that book, or a page that you would need to be a registered member to access and it has subsequently thrown up that 'error' report. Considering the error message you have posted, it does look site customised.

Member Avatar for Member #1048311

Latest SEO techniques... very clever, everybody clicks...

Member Avatar for Joe2

The URL I am searching is contained in an email from a trusted source. I have tried using the URL as a Google search in Firefox 18 (default browser), IE8 and Chrome. I have also tried usung the address bar to search in the three browsers with the same result.

Member Avatar for BigPaw

@EveryAuction

Latest SEO techniques... very clever, everybody clicks.

I thought this too initially, but then checked his post history, and there is no history of spam.

The URL I am searching is contained in an email from a trusted source.

The link you posted here worked fine for me. Try this link instead.

Edited by BigPaw
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.