virtualmin/webmin login no ssl

19 posts / 0 new
Last post
#1 Sun, 06/08/2008 - 04:46
Maurizio1230

virtualmin/webmin login no ssl

Hi all,

http://hostinvent.com:10000

When I login on this page I get this message

Error Bad Request This web server is running in SSL mode. Try the URl https://ns2.fx3432.hostinvent.com/ instead.

What is this https://ns2.fx3432.hostinvent.com/ ?

I don't find any connection in bind server between ns2 and fx3432 :( I can say fx3432.hostinvent.com is our system hostname.

I'd like to change it to https://fx3432.hostinvent.com/

Thank you very much<br><br>Post edited by: Maurizio1230, at: 2008/06/08 04:47

Sun, 06/08/2008 - 10:43
trendzetter

I looked up your PTR record:
host 87.118.101.155
155.101.118.87.in-addr.arpa domain name pointer ns2.fx3432.hostinvent.com.

Ask Hostinvent.com to change the PTR record to fx3432.hostinvent.com.

Sun, 06/08/2008 - 19:32 (Reply to #2)
sgrayban

PTR as in the reverse for the IP.

Sun, 06/08/2008 - 19:33 (Reply to #3)
sgrayban

How ever you can use fx3432.hostinvent.com because its still the same IP.

$ host fx3432.hostinvent.com
fx3432.hostinvent.com has address 87.118.101.155
fx3432.hostinvent.com mail is handled by 5 mail.fx3432.hostinvent.com.

Sun, 06/08/2008 - 23:13 (Reply to #4)
Maurizio1230

How can I change this PTR record?

Mon, 06/09/2008 - 11:17 (Reply to #5)
Joe
Joe's picture

<div class='quote'>How can I change this PTR record?</div>

You probably can't. Reverse resolution is usually handled by your hosting provider or ISP, and that's usually fine. As long as the names resolve back and forth correctly, it doesn't matter at all what name an IP resolves to. But, if the name resolves back to something else, it's a problem and will prevent mail delivery (and cause other problems). If that's the case, you'll need to get your provider to correct the record.

--

Check out the forum guidelines!

Mon, 06/09/2008 - 13:14 (Reply to #6)
Joe
Joe's picture

BTW-If you just want Webmin to direct you to a different name, that can be done in the Webmin configuration. Look in Webmin:Webmin:Webmin Configuration:Ports and Addresses and set the option labeled &quot;Web server hostname&quot; to whatever name you want.

--

Check out the forum guidelines!

Mon, 06/09/2008 - 22:35 (Reply to #7)
Maurizio1230

Do you advice me to have the PTR record changed to fx3432.hostinvent.com?

Thanks Joe

Tue, 06/10/2008 - 00:19 (Reply to #8)
Joe
Joe's picture

<div class='quote'>Do you advice me to have the PTR record changed to fx3432.hostinvent.com?</div>

Probably. It's <i>their</i> network...they ought to know what sane values are. It's currently wrong, though, for sure, since it points to a name that does not resolve (ns2.fx3432.hostinvent.com, as Scott explained). That's broken, so they need to fix it to something that does resolve, and it appears fx3432.hostinvent.com does resolve correctly. So, yes. Ask your host to fix the PTR for that IP.

--

Check out the forum guidelines!

Tue, 06/10/2008 - 00:45 (Reply to #9)
sgrayban

Forward dns <b>MUST</b> match the reverse. I have seen to many mail servers setup wrong and mail bounced just for this reason.

If the hostname for your mail server is -- foo.com then the reverse for the IP <b>MUST</b> be foo.com

Example:
$ host spock.borgnet.us
spock.borgnet.us has address 204.96.138.100

$ host 204.96.138.100
100.138.96.204.in-addr.arpa domain name pointer spock.borgnet.us.

Tue, 06/10/2008 - 11:28 (Reply to #10)
Joe
Joe's picture

<div class='quote'>Forward dns MUST match the reverse. I have seen to many mail servers setup wrong and mail bounced just for this reason.</div>

Not quite right.

There can be thousands of forward DNS records that point to a single IP. There will only ever be one reverse. The forwards cannot <i>all</i> match the reverse.

The reverse record must resolve to a forward address that resolves back to the IP. That's the <i>only</i> requirement for a PTR records.

For example, virtualmin.com has this PTR:

[joe@delilah ~]$ host 70.86.4.238
238.4.86.70.in-addr.arpa domain name pointer ee.4.5646.static.theplanet.com.

And that name resolves back to:

[joe@delilah ~]$ host ee.4.5646.static.theplanet.com
ee.4.5646.static.theplanet.com has address 70.86.4.238

That's all that matters. The PTR does not have to be &quot;virtualmin.com&quot; or &quot;mail.virtualmin.com&quot; or any of the dozens of other names system system has. It can be something wholly unrelated to my system--in this case a standard name in the pool of names theplanet uses for reverse resolution.

Reverse resolution is dead simple and it doesn't matter what names are being used--but it has to work, in both directions, or mail will bounce.

--

Check out the forum guidelines!

Tue, 06/10/2008 - 22:20 (Reply to #11)
sgrayban

I meant if the mail server is using <b>foo.om</b> then the reverse must match that because more and more mailservers are rejecting mis-matched forward-reverse.

Wed, 06/11/2008 - 12:00 (Reply to #12)
Joe
Joe's picture

Hmmm...Are they? I haven't noticed an increase in bounces from our system. But it could be a &quot;spammy&quot; characteristic for some servers, I guess. But it's still extremely common for reverse resolution to not be delegated to the customer at colo and dedicated server hosting facilities that it seems like one would bounce an awful lot of mail if you used a rule like that.

--

Check out the forum guidelines!

Wed, 06/11/2008 - 12:24 (Reply to #13)
sgrayban

AOL and Yahoo are known to reject mis-matched forward-reverse and M$ hotmail/msn always reject it.

Thu, 06/12/2008 - 05:05
Maurizio1230

sorry but what do you advice me to choose? I have two ip on this server.

87.118.101.155 hostinvent.com PRT-ns2.fx3432.hostinvent.com
87.118.100.155 shared by all others site. PRT-ns.fx3432.hostinvent.com

Thank you very much
Maurizio1230

Thu, 06/12/2008 - 12:40 (Reply to #15)
Joe
Joe's picture

What do you mean? What's to choose? They both ought to resolve correctly, and it appears neither does. But Postfix will send generally outgoing mail via the &quot;default&quot; interface--usually eth0--though the routing table on the system can alter that.

And both of your mentioned PTR records fail to resolve. You need a PTR record on whatever IP is your default route, and it needs to resolve to the correct IP. (Again, the name used in the reverse record is irrelevant, as far as I know..though Scott has asserted otherwise, and I don't know enough to argue strongly one way or the other...but I've never cared about what name, and I've never had problems with mail bouncing, including to Hotmail, AOL, and Yahoo--we have customers with all of those addresses here at Virtualmin.com, and our reverse resolves to e2.4.5646.static.theplanet.com and the mail server claims to be virtualmin.com or mail.virtualmin.com or something along those lines).

So who is &quot;hostinvent.com&quot;? Is that your hosting provider, or is that you? I'm now unsure whether we're looking at provider generated reverse records, or delegated records that you haven't configured correctly.

--

Check out the forum guidelines!

Fri, 06/13/2008 - 09:16 (Reply to #16)
Maurizio1230

Now I understand. I create two A records pointed to my two domains.
May you check if the A records resolve to the correct IP.

Thanks Joe.

Fri, 06/13/2008 - 09:22 (Reply to #17)
Maurizio1230

Edit:*....pointed to my two ip.

Sun, 06/05/2016 - 15:13
eagleyed
eagleyed's picture

I'm gettting the ssl error message and have installed the manual way and by using the script. No matter what I do still can't actually fully login to Virtualmin. Username and password is accepted and all I'm seeing is a blue circular motion on the screen and NEVER actually logs in. Was getting an error message such as missing "Perl module Authen" and I installed that. As for a ptr record don't understand why I can't login to Virtualmin by ip as I can do that with Webmin. Using Centos 6.8 & 7 and still get the same result as listed above. Any help would be appreciated! ****Mods delete this post as it's getting no replies.