Oh noes Site fails to open stream (403)

  • Topic: Bug 
  • Thread starter Thread starter Hobin
  • Start date Start date
Join the discussion
Registration is free. Start your own thread to ask a follow-up.
Sign up Log in
5 replies · 4K views
Hobin
Messages
137
Reaction score
2
[SOLVED] Oh noes! Site fails to open stream (403)

When I open physicsforums.com, I get the following error at the top of the page:

Code: 
Warning: file_get_contents(https://www.physicsforums.com/external.php?type=rss2&forumids=186) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden in [path]/includes/init.php(304) : eval()'d code on line 218

Warning: file_get_contents(https://www.physicsforums.com/external.php?type=rss2&forumids=186) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden in [path]/includes/init.php(304) : eval()'d code on line 218

Warning: file_get_contents(https://www.physicsforums.com/external.php?type=rss2&forumids=186) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden in [path]/includes/init.php(304) : eval()'d code on line 218

Warning: file_get_contents(https://www.physicsforums.com/external.php?type=rss2&forumids=186) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden in [path]/includes/init.php(304) : eval()'d code on line 218

The site seems to work fine, but it looks ugly nonetheless. I'm wondering if anyone else's having this error, or if someone's currently making modifications to the site. This is the first time I got this error. I checked the site about three hours ago, too, and I didn't get an error at that time.

EDIT: I only get this at the index page, not in any of the boards/threads.
 
Last edited:
Physics news on Phys.org

Discussion

Same here (using chrome), only at the first screen though.
 
Andre said:
(using chrome)
I don't think it's browser related. The warning is clearly from a server-side script, so the only way it wouldn't show in another browser is if it wouldn't display such warnings on default (which is just plain wrong).

But, maybe I'm wrong. I don't know if everyone's getting these warnings, after all.