Welcome Guest. Please Login or Register  


You are here: Index > Webuzo > General Support > Topic : Webuzo behind Firewall and One-to-One Nat



Threaded Mode | Print  

 Webuzo behind Firewall and One-to-One Nat (12 Replies, Read 14945 times)
kellenw
Group: Member
Post Group: Newbie
Posts: 25
Status:
I am trying to run Webuzo on Ubuntu in a hyper-v VM.  The VM has a private IP (192.168.x.x) on eth0 that is then bonded to a public IP (72.22.x.x) using one-to-one Nat on a Cisco RV325 router. I have a domain name (ie. somerandomdomain.com) with ns1 and ns2 nameservers pointing to the public IP (72.22.x.x). Any chance someone could provide a brief "how to" on preparing a fresh install of Ubuntu for installing Webuzo and then setting up IP and dns settings in Webuzo?  I've installed it and thought I did the right things, but I run into problems after a system reboot.  The domain will not work, but using the public IP (72.22.x.x) still does.  If I uninstall and reinstall the LAMP stack through Webuzo, the domain name will generally start working, until I reboot again.  Odd.... But I'm thinking maybe I've got something setup wrong regarding DNS and IP settings, or maybe it's just a bug.  Also probably worth noting, when the domain does not respond, I notice that clicking on the "SERVICES" icon in Webuzo will not pull up the services status screen either. It just keeps trying to load. If I reboot during the loading of the services page, it actually loads the page as Ubuntu goes through the reboot sequence.
IP: --   

Webuzo behind Firewall and One-to-One Nat
valley
Group: Webuzo Team
Post Group: Super Member
Posts: 1644
Status:
Hi,

Instead of re-installing LAMP, try restarting the services.

Hope it helps :)

-----------------------
Webuzo : Single User Control Panel
Join Webuzo :
Facebook
Twitter

IP: --   

Webuzo behind Firewall and One-to-One Nat
kellenw
Group: Member
Post Group: Newbie
Posts: 25
Status:
Hi Valley,

Thanks for replying.

My problem is that the domain does not work after I reboot the server. Also, clicking on the services icon in Webuzo does not load up the services page after I have rebooted.

If I remove the LAMP stack and then reinstall it (in Webuzo), the domain begins working again and the services page will load correctly, until I reboot the system. Once I reboot, the domain quits responding again, and the services page will not load.

It seems like there is some kind of issue with apache, but I can't figure it out.  It is just so strange that it works right away following installing the LAMP stack, but then fails once I reboot the server.
IP: --   

Webuzo behind Firewall and One-to-One Nat
valley
Group: Webuzo Team
Post Group: Super Member
Posts: 1644
Status:
It seems are services are not restarted after a reboot.

We shall replicate the issue on our test servers and provide a solution ASAP

-----------------------
Webuzo : Single User Control Panel
Join Webuzo :
Facebook
Twitter

IP: --   

Webuzo behind Firewall and One-to-One Nat
kellenw
Group: Member
Post Group: Newbie
Posts: 25
Status:
Thanks again for replying. I'm not sure that's the problem though. I think it may simply be an issue with DNS and IP settings that are causing some sort of issue.

To further investigate the problem, I uninstalled all Webuzo Apps and then re-installed Webuzo.  Things appeared to work as expected following the reinstall. The default website came up with the usual Webuzo placeholder page (good).  I was able to access the services page (good).  However, after I restarted apache, the default domain no longer worked.  I returned to the end user panel homepage and then attempted to click on services, and it would not respond.  In other words, if I reboot the server OR restart apache, something goes wrong.

I am thinking the problem is being caused by the server residing behind a NAT router and using one-to-one NAT to map one of our available public IP's from our block.  I am starting to think that either apache or webuzo is getting confused between the private IP on eth0 and the public IP that is mapped to it.

-=ROUTER (Cisco RV325)=-
- DHCP server on 192.168.2.1
- Public static IP 72.22.x.1 (used by DHCP clients)
- I have 10 sequential static public IP's available to my account to use/assign as I need.
- I use one-to-one NAT to assign static public IP's to servers behind the router.

-=UBUNTU SERVER RUNNING WEBUZO=-
- eth0 is on a static private IP 192.168.2.156 that it receives from the dhcp server on the Cisco router via MAC to IP binding.
- Public static IP 72.22.x.8 is mapped to the private IP above using one-to-one NAT on the Cisco router. In other words, public 72.22.x.8 routes to private 192.168.2.156.  All ports are open at the router.
- ns1.myhost.com and ns2.myhost.com (not actual domain, but used for illustration purposes) are setup with godaddy and pointing to 72.22.x.8, as they should.
- Hostname and FQDN are setup in ubuntu /etc/hosts file correctly I believe.

-=WEBUZO ADMIN CP>>SETTINGS>>NAMESERVERS=-
- Primary IP - I have tried using the one-to-one nat public IP (72.22.x.8) as well as the private IP (192.168.2.156).  My assumption is that the public IP (72.22.x.8) should be used here, but thought I'd try both, considering my difficulties.
- Primary Domain - I have myhost.com in this field.
- NS1/NS2 - I have ns1.myhost.com and ns2.myhost.com in these fields, respectively.


Any ideas? :)
IP: --   

Webuzo behind Firewall and One-to-One Nat
kellenw
Group: Member
Post Group: Newbie
Posts: 25
Status:
UPDATE: I uninstalled the LAMP stack and installed the LEMP stack instead.  Everything works as it should following system reboots or service restarts.  The problem certainly seems to be linked to apache somehow.
IP: --   

Webuzo behind Firewall and One-to-One Nat
kellenw
Group: Member
Post Group: Newbie
Posts: 25
Status:
ADDITIONAL UPDATE: LEMP stack does appear to work 100% correctly, but I need to run Apache due to some script requirements.  So, I tried installing just Apache (not the full LAMP stack) with the 100% working LEMP stack already installed.  I chose to make Apache the default webserver app during installation.  The domain quit working.  I removed Apache, and then the domain worked again.  The problem is definitely linked to Apache somehow.  Maybe a bug in the Apache and LAMP installation and auto-configuring routine within the current version of Webuzo?
IP: --   

Webuzo behind Firewall and One-to-One Nat
valley
Group: Webuzo Team
Post Group: Super Member
Posts: 1644
Status:
Are you on Ubuntu ?

Remove Python2 from the Webuzo Enduser Panel

Is the Apache services active on port 80 ?

Root > lsof -i :80

Let me know the results.

-----------------------
Webuzo : Single User Control Panel
Join Webuzo :
Facebook
Twitter

IP: --   

Webuzo behind Firewall and One-to-One Nat
kellenw
Group: Member
Post Group: Newbie
Posts: 25
Status:
Hi Valley,

Yes, the server is Ubuntu 14.04 LTS.  Good idea on checking if Apache is listening on port 80.  It is, but only TYPE: IPV6.  When using lsof -i :80, I only get apache instances listening on IPV6, but there are no IPV4 entries.  Obviously, that's going to cause problems. :)

I was curious, so also tried Webuzo on CentOS 7 minimal.  I got the same results (IPV6 only using LAMP stack).

LEMP stack worked correctly on both Ubuntu and Centos.  Only LAMP/Apache seems to have this problem.
IP: --   

Webuzo behind Firewall and One-to-One Nat
valley
Group: Webuzo Team
Post Group: Super Member
Posts: 1644
Status:
Apology for the inconvenience.
We shall replicate the issue on our development servers and provide a solution ASAP.

-----------------------
Webuzo : Single User Control Panel
Join Webuzo :
Facebook
Twitter

IP: --   

Webuzo behind Firewall and One-to-One Nat
kellenw
Group: Member
Post Group: Newbie
Posts: 25
Status:
Hi @valley,

Any update on this?  It's the only thing holding me back from signing up for a webuzo license.

Thanks,
kellenw
IP: --   

Webuzo behind Firewall and One-to-One Nat
valley
Group: Webuzo Team
Post Group: Super Member
Posts: 1644
Status:
Quote From : kellenw January 21, 2015, 4:55 am
Hi @valley,

Any update on this?  It's the only thing holding me back from signing up for a webuzo license.

Thanks,
kellenw


Though it shows up only IPv6, it does serve to IPv4 as well
You can test one and confirm the same.

Let us know the issue that you face.



-----------------------
Webuzo : Single User Control Panel
Join Webuzo :
Facebook
Twitter

IP: --   

Webuzo behind Firewall and One-to-One Nat
phinedemolish
Group: Member
Post Group: Newbie
Posts: 3
Status:

    hi there, i have a server behind my firewall / router. the server now
is having Private IP Address (10.0.0.12). I've made port-forwarding
setting on my router, so i could access my server remotely with my
Public IP Address (112.78.xxx.43). The remote installation process was
going well. once finish, we have to setup via web browser
(112.78.xxx.43:2004). Here's the problem, when I access
112.78.xxx.43:2004, URL on the web browser suddenly changed into
10.0.0.12:2004 and the process was interrupted. if there's any way to
fix this installation?Thanks for your kind attention guys
IP: --   

« Previous    Next »

Threaded Mode | Print  



Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is March 19, 2024, 7:12 am.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 11  |  Page Created In:0.026