XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Modules Support forums / 
  3. Module troubleshooting 
  4.  / Unable to get headlines module working from behind firewall
Register
1
rifraff
Unable to get headlines module working from behind firewall

  • 2004/10/19 15:32

  • rifraff

  • Just popping in

  • Posts: 67

  • Since: 2003/4/16


Hello,

I am unable to get the XOOPS Headlines modules working from our system behind our firewall.

Firewall Information:

Our web server is NAT'd behind our firewall.
Our web server is accessed via port 80.
Our web server can connect out to other web sites
via port 80.
Our web server can IP Masquerade out from behind
the firewall.

The XOOPS Headlines module works fine on a test box
that is not behind a firewall.

Thanks,

Brian Reifsnyder
breifsnyde@state.pa.us
2
ackbarr
Re:Unable to get headlines module working from behind firewall

if you enable php debugging, do you get any error messages when accessing a page that uses the headlines module?
3
rifraff
Re:Unable to get headlines module working from behind firewall

  • 2004/10/19 15:43

  • rifraff

  • Just popping in

  • Posts: 67

  • Since: 2003/4/16


I get the following messages:


Warning [PHP]: fopen() [function.fopen]: php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in file modules/xoopsheadline/class/headlinerenderer.php line 62
Warning [PHP]: fopen(http://www.xmlhack.com/rss10.php?cat=30) [function.fopen]: failed to create stream: Resource temporarily unavailable in file modules/xoopsheadline/class/headlinerenderer.php line 62



This almost sounds like a DNS issue. But, I can ping sites outside the firewall (i.e. google.com, yahoo.com) using their host name. So I don't see how that is the problem.

Thanks,

Brian
4
rifraff
Re:Unable to get headlines module working from behind firewall

  • 2004/10/19 15:47

  • rifraff

  • Just popping in

  • Posts: 67

  • Since: 2003/4/16


Additional Information (before anyone asks. )


The allow_url_fopen, in the php.ini is set to On.
I tried replacing the saxparser.php, without success.


Thanks,

Brian
5
tl
Re:Unable to get headlines module working from behind firewall

  • 2004/10/19 16:22

  • tl

  • Friend of XOOPS

  • Posts: 999

  • Since: 2002/6/23


Your firewall may have blocked fopen access even though you had set it open on the server - just a guess.

You may want to try snoopy instead to retrieve contents. See GIJOE's hack

http://www.peak.ne.jp/xoops/modules/news/article.php?storyid=20

You can download the hacked file from XOOPS Tips if you wish.
6
rifraff
Re:Unable to get headlines module working from behind firewall

  • 2004/10/19 17:25

  • rifraff

  • Just popping in

  • Posts: 67

  • Since: 2003/4/16


Ok, I tried snoopy and it didn't work either.

I did, however, notice that when I attempted to add an RSS feed that after I clicked the submit button I had the following error on the screen that appears for about 2 seconds immediately after hitting the submit button.


Warning [PHP]: fopen() [function.fopen]: php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in file modules/xoopsheadline/class/headlinerenderer.php line 62

Warning [PHP]: fopen(https://xoops.org/backend.php) [function.fopen]: failed to create stream: Resource temporarily unavailable in file modules/xoopsheadline/class/headlinerenderer.php line 62



The above messages seem to indicate that the name resolution failed. This is perplexing because I can resolve the host names from the command line with ping or the lynx web browser. Is there something, perhaps in the php.ini file, that I may need to set to point to the DNS as well?

Thanks,

Brian
7
ackbarr
Re:Unable to get headlines module working from behind firewall

Just found this buried in the fopen() function notes on php.net

Quote:

If you're having problems with fopen("url...") but you can run 'host url' in a shell window and get the correct lookup, here's why...

This has had me banging my head against it all day - finally I found the answer buried in the bug reports, but figured it should really be more prominent!

The problem happens when you're on an ADSL line with DHCP (like our office)... When the ADSL modem renews the DHCP lease, you can also switch DNS servers, which confuses apache (and hence PHP) - meaning that you can't look up hosts from within PHP, even though you *can* from the commandline.... The short-term solution is to restart apache.

You'll get "php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in ..." messages as symptoms. Restart apache, and they're gone

Simon
8
tl
Re:Unable to get headlines module working from behind firewall

  • 2004/10/19 17:42

  • tl

  • Friend of XOOPS

  • Posts: 999

  • Since: 2002/6/23


This is a known problem of fopen with firewall. You might find a solution by searching Google on "fopen firewall". Many people are having the same problem.

BTW, did you get any error messages using Snoopy?

[edit] well, ackbarr found a solution for you. [/edit]
9
rifraff
Re:Unable to get headlines module working from behind firewall

  • 2004/10/19 18:01

  • rifraff

  • Just popping in

  • Posts: 67

  • Since: 2003/4/16


I also found the message on php.net and tried resetting apache with a "./rc.httpd restart" and was unsucessful.

So, I tried "./rc.httpd stop" followed by a "./rc.httpd start" and was successful!!!!

As to why a restart didn't work and a manual stop and start worked....I don't have a clue.

Snoopy also reported a similar name resolution problem; but works now as well.


Thanks for all the help.

Brian

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

444 user(s) are online (315 user(s) are browsing Support Forums)

Members: 0

Guests: 444

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits