Skip to main content

Website

Posted by civey on Mon, 02/07/2011

I am having issues with the log in to my thirdlane server.
If I put the IP address of the server it will let me log into the system fine. But if I enter the www.name of the server it will bring me to the server login screen but it will not let me log into the system until I reduce the privacy setting to low in Internet Explorer.

This works no problem in Fire fox but as we all know most customers will be using IE.

Thanks


Submitted by eeman on Mon, 02/07/2011 Permalink

ive never had that problem on any box i've ever built. Your question is actually more related to webmin not thirdlane, the web engine itself is webmin. However, I would strongly encourage you to use SSL encryption of your portal so the passwords are not sent in plain text. See if turning on SSL resolves your issue. Granted if you self-sign your certificate, you'll have to click the warning in IE every visit (unlike Firefox that lets you keep the certificate), but you shouldn't have to downgrade privacy settings.

FWIW I encourage everyone I know to not use IE. Not a month goes by where another 'OMFG update now or bug XYZ will grant remote access to everything you own!' bug comes to light. I don't care if they use google chrome, firefox, safari, or Opera; as long as its not IE :-)

Submitted by civey on Fri, 02/11/2011 Permalink

I was able to get this kinda working.

We are now running SSL, with a cert that we bought for the server.

2 things that I don't like and was wondering if someone could help.

We have to enter https://www.websitename.com:10000

Can we make it where we dont need the port 10000 at the end?

Also I would like to Mask the web address, So instead of it digging into the system it just shows www.websitename.com at the top the whole time.

Thanks

Submitted by civey on Mon, 02/14/2011 Permalink

I am not Lazy and I have been using Google.
I don't understand why people such as you would not just read a post and then move on instead trying to piss someone off with remarks about their post.

If you don't like the way I post or the questions I ask then don't read them.

Submitted by dozment on Mon, 02/14/2011 Permalink

Create a file called index.html with the following in your web server's root directory:


Change "YOURWEBSERVER.COM"to your URL. When users browse to your site and open the default index.html file it will redirect them to the webmin page.

Submitted by justdave on Wed, 02/16/2011 Permalink

As long as you're not also running a web server on port 443, you can always just tell webmin to run on port 443 instead of port 10000. That'll make the port number go away in the URL. If you are running a web server already, there's ways around that, too.

In our case we're running a couple other things on the same server (mostly still phone related, but home-brew cgi scripts and http-based provisioning that we set up before Thirdlane directly supported that, etc), so we let Apache listen on port 443 and proxy to webmin from there.

Apache since version 2.0 has supported built-in reverse-proxy via the mod_proxy module.

We have webmin listening in cleartext on port 10000, but set up so it only listens on localhost and not on any of the external IPs.

We then have something like this in the <VirtualHost _default_:443> block:


SSLEngine On
ProxyPass /cgi-bin !
ProxyPass / http://localhost:10000/
ProxyPassReverse / http://localhost:10000/

The ! on the end of the cgi-bin line tells it *not* to proxy that pathname, the following two lines proxy everything else to the webmin server. This lets Apache take care of the SSL for us, and also lets us run other things besides PBX Manager on the same hostname (by adding the subdirectories for those programs in a ProxyPass line with the ! on the end)

Submitted by eeman on Wed, 02/16/2011 Permalink

for those of you running the latest ISO I would not advise changing webmin's listening port since apache is part of your provisioning process. It supports FTP,TFTP, HTTP, _and_ HTTPS provisioning.