Strange redirect to https://www.none.com/

[artichoke]

Strange redirect to https://none/

When I add a new subdomain from the DirectAdmin menus, the subdomain gets added, and then my web browser is redirected to https://www.none.com/. If I go past the SSL certificate warning caused by that URL, then my browser is further redirected to http://www.sitelauncher.com/, which tries to sell me web design services.

I experienced this odd new behavior on two different servers running DirectAdmin.

I checked recent DirectAdmin revision announcements and saw no mention of any such new feature.

I wonder if anybody else has observed this, and if so, why you think this might happen?

Rahul

 

[floyd]

I checked recent DirectAdmin revision announcements and saw no mention of any such new feature.

That is because this is not a DA feature/problem. You need to talk to your hosting provider or domain registrar.

 

[artichoke]

I made slight progress in tracking down this behavior. My web browser (Opera) was taking a URL like "https://none/" and changing it to "https://www.none.com/". I switched off this misbehavior, and now, when I add or remove a subdomain within DirectAdmin, the browser is merely redirected to "https://none/". So there is no deliberate attempt to sell any services, just an incorrect redirection to "https://none/".

Doing

strings -a /usr/local/directadmin/directadmin | grep -i -w 'none'

yields some hits, so it's quite possible that DirectAdmin is for some reason sending "https://none/".

And by the way, I'm looking for technically helpful answers with diagnostic suggestions, not just random speculation as to who to talk to.

Rahul

 

[floyd]

And by the way, I'm looking for technically helpful answers with diagnostic suggestions, not just random speculation as to who to talk to.

It was not random speculation. Based on your original post the problem probably did not have anything to do with your server at all and certainly not DirectAdmin. My suggestion was to talk to your host or domain registrar and ask them why they were doing this redirection.

Now you have given us more information. Its still not a DirectAdmin problem since DirectAdmin does not answer to normal web requests. It only answers on port 2222 so if the url does not have :2222 in it then DirectAdmin is not doing anything to it.

You still have not given us the actual url that is being redirected to https://none/ which makes it impossible for us to help you any further.

When doing any time of domain diagnosis we first have to make sure that its a registered domain. Then we have to make sure that its indeed pointing to your server. Then we type it into a browser and see what happens.

You telling us that all this is correct does not help. We have to check it ourselves.

So in order to give you technical things to look for and not give you mere speculation you have to one give us the problem domain and give us the ip address its supposed to be going to. It would also be helpful to know the nameservers it is supposed to be going to to.

Without real data we cannot give you real answers.

 

[floyd]

I made slight progress in tracking down this behavior. My web browser (Opera) was taking a URL like "https://none/" and changing it to "https://www.none.com/".

That can be considered normal behavior for a browser to add the www if www is part of the virtual server name in the configuration file.

 

[artichoke]

I'm afraid I don't see the point in the assertion "You still have not given us the actual url that is being redirected to https://none/ which makes it impossible for us to help you any further".

I thought my original posting was quite clear that I see the misbehavior while I am at the DirectAdmin GUI. I see no ambiguity in my statement, "When I add a new subdomain from the DirectAdmin menus, the subdomain gets added, and then my web browser is redirected to https://www.none.com/.".

If I am successfully using the DirectAdmin GUI, then I must be pointing my browser to a valid domain. And since I stated that I see the same behavior on two different servers, it must be the case that I have tested this with two different domains (each server having a domain of its own).

Nothing justifies your statement "Its still not a DirectAdmin problem since DirectAdmin does not answer to normal web requests. It only answers on port 2222 so if the url does not have :2222 in it then DirectAdmin is not doing anything to it."

A bug in DirectAdmin could easily cause it to complete adding a subdomain and then send a browser redirect causing the browser to go to https://none/. We don't know there is such a bug, but you haven't provided any technically sound reasoning for your blanket assertion that it's not happening.

In fact, you haven't provided any technically sound reasoning for anything you have stated so far.

Just in case it's still not clear, I will appreciate helpful responses based on a technically sound analysis.

And by the way DirectAdmin 1.29.1 is in use here on both servers.

Rahul

 

[floyd]

I thought my original posting was quite clear

It wasn't that clear to me. I misunderstood your problem. I thought when trying to go to the subdomain you were being redirected. I didn't know it was from within the directadmin gui. I have never seen that before and I have been using DA for two years which include the version you are running now. Try updating DA and see if that helps. If not then you need to email directadmin for support on that if nobody here can answer you.