Thousands of verified Experts are ready to answer your specific questions 24/7.
Satisfaction is guaranteed and you pay your Expert only if you are satisfied.
Just type your detailed question and click "Get an Answer."
In minutes you'll get a response from an Expert. You can always ask follow-up questions.
Happy with your answer? Just click "Accept" to pay your Expert.
I have Squid and Webmin installed and running on a remotely-hosted server (Fedora Core 6). I cannot access the server through https://xxx.xxx.xxx.xxx:10000/. Not sure but I suspect this is a firewall/port issue.
Optional Information: OS: Windows XP; Browser: FirefoxAlready Tried: I am using Windows XP with Firefox. I can access the server using PuTTY (logged in as root).
hello! 1) So this server is on your local network, or you have already worked out translating a public address to a private address, seeing as putty works. putty's SSL port is going to be open by default most of the time. Get a terminal screen on the linux computer and issue the command (you must be root)service iptables statusIf you get a long feed of lines, or can recognize that it is running, turn it off (just for testing purposes, we'll turn it back on after we get things working). service iptables stopTry to connect to your application now. Also, make sure that Squid and webmin .conf files are all configured correctly. Hopefully this will get you pointed in the right direction. If the firewall issue doesn't help, than we'll work on something else. 2) You don't have any security appliances that would allow SSL based programs, but nothing else to pass through in between you and the box do you? Answer my 2 questions with the numbers that are bold. We'll go from there.
Technology Diagnostician
SMB / Enterprise security, Oracle Databases, Linux administration, Web Design, Joomla Expert
Thank you Branden, I have been trying to figure this out on my own for hours and hours. But I know nothing about Linux. I'll do my best to reply in a way that makes sense to us both 1. This is a dedicated server hosted halfway across the country. I downloaded PuTTY, and connected using the server IP (host 22, SSH-type connection). service iptables status Firewall is stopped. I then tried system-config-securitylevel-tui (enabled firewall) iptables -I RH-Firewall-1-INPUT 6 -m state --state NEW -m tcp -p icp --dport 10000 -j ACCEPT iptables-save > /etc/sysconfig/iptables service iptables status Which gave me the long line of feeds. I have since restarted the server, so the firewall is back off. "Also, make sure that Squid and webmin .conf files are all configured correctly." I have no idea if they are configured correctly. 2. I have no idea, so probably not.
Very nice explanations. I wish everyone responded like that! Well, if the server is half way across the country, then there is most DEFINITELY security appliances between you and the machine. Most of which have no affect, but if this server is hosted by a company that provides a service, than they probably have every port locked down except for SSH. If you are using putty to connect to the server. You can use the tunnel function in putty, to create a tunnel to the server. In this case, even if the server is locked down, you should be able to access the web page you desire by piggy-backing over SSH.
Thank you, XXXXX XXXXX we're almost there. Here is what nmap tells me: Starting Nmap 4.52 ( http://insecure.org ) at 2008-01-11 13:11 Central Standard Time Initiating Ping Scan at 13:11 Scanning 66.36.229.88 [2 ports] Completed Ping Scan at 13:11, 0.16s elapsed (1 total hosts) Initiating Parallel DNS resolution of 1 host. at 13:11 Completed Parallel DNS resolution of 1 host. at 13:11, 0.03s elapsed Initiating SYN Stealth Scan at 13:11 Scanning 66.36.229.88 [1714 ports] Discovered open port 22/tcp on 66.36.229.88 Completed SYN Stealth Scan at 13:11, 9.63s elapsed (1714 total ports) Host 66.36.229.88 appears to be up ... good. Interesting ports on 66.36.229.88: Not shown: 1711 filtered ports PORT STATE SERVICE 22/tcp open ssh 443/tcp closed https 631/tcp closed ipp That looks like 443 (https) is closed. Does that need to be fixed first? If so, how?
Yeah thats telling us that only SSH is open. Using the tunnel should get you in. Unless you can ask who ever owns the hardware or Connection service to open up 443. Nmap. I'm impressed. Had I known you had that kind of knowledge, I would have suggested it! Most people who come here would reply."wut is nmap i dun c wat it ha sto withm y problem."Which Is why I enjoy my time with people like yourself. Full sentences are so refreshing! Good luck
Okay, I'll give this a shot. Half the stuff I wrote (including nmap) makes absolutely no sense to me. I just find stuff online, and if it sounds related I give it a shot. Like a bull in a china shop, I know. So far nothing broken, so that's good. I'll follow-up shortly.
Let me know how it works out. I'll be checking periodically this weekend.
I was unable to get through using port 443, but someone else I was asking for help suggested I use port 80 (which did work). I appreciate your help and will accept your answer. Sean