The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Using IP to "see" website results in URL changing to unrelated domain name...

Discussion in 'General Discussion' started by electric, Oct 4, 2005.

  1. electric

    electric Well-Known Member

    Joined:
    Nov 5, 2001
    Messages:
    697
    Likes Received:
    1
    Trophy Points:
    18
    We have a reseller who signed up a new customer, and then the customer went to their site... http://IP/~username

    (They wanted to see their site before they load up content and transfer the domain/change the nameservers.)

    It resolved to this:


    http://www.SomeDomain.com/~username/


    And lists:


    Apache/1.3.33 Server at www.SomeDomain.com Port 80


    At the bottom.

    Now, the problem is that "SomeDomain.com" is another customer of ours.. .and has nothing to do with us or our website, and is VERY confusing to our new customer.

    Why is this happening? I believe it's because our resellers use shared IPs, so all their domains use the same IP...

    Can we fix it? Perhaps it's possible for WHM to give each reseller the ability to specify the "first domain in the list" for their shared IP? This way, the reseller can pick which domain they want to be shown in this situation... (or perhaps even just a blank page)
     
  2. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    It's not a cPanel issue but is the way in which Apache works. If you don't specify a domain name and use the IP instead it will use the details from the first virtualhost container it comes across that uses that IP address. So, if you want to change the behaviour then you need to rejig the order of the virtualhost containers in httpd.conf and/or create a minimal container similar to the one that's normally created for the servers main IP address.
     
  3. electric

    electric Well-Known Member

    Joined:
    Nov 5, 2001
    Messages:
    697
    Likes Received:
    1
    Trophy Points:
    18
    Thanks!

    Do you think this is something that could be added as a feature in WHM? (ie: Ability for reseller to "jig" the apache config file to pick which account is listed "first"?)

    Let me know if you think it's worth it and I'll create a new request at bugzilla..
     
  4. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    I would imagine anything is possible. To make it more universal you could suggest an option to have a basic virtualhost setup as per the main IP address for all IP addresses on the server as they're added to tbe the first that appears in httpd.conf
     
  5. electric

    electric Well-Known Member

    Joined:
    Nov 5, 2001
    Messages:
    697
    Likes Received:
    1
    Trophy Points:
    18
  6. net-trend

    net-trend Member

    Joined:
    Sep 17, 2002
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    I am having this issue with EA3. After manually rearranging the virtualhost I want displayed for the IP, the apache distiller rearranges it back and shows the wrong site again.

    Anyone have any ideas on how to resolve this on EA3?
     
  7. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    I am surprised it only has 1 vote. I know browsing these forums, this seems to be a very frequently requested feature (though in the past most have simply manipulated httpd.conf so the first entry was what they wanted to be).
     
  8. electric

    electric Well-Known Member

    Joined:
    Nov 5, 2001
    Messages:
    697
    Likes Received:
    1
    Trophy Points:
    18
    David, I don't mean to be rude...

    ... but if you notice a disparity between the number of votes in bugzilla and the number of times that same feature is requested in the forums.. then this most likely means the following:

    - the majority of people visiting the forums don't have a clue that bugzilla even exists.
    - People who know bugzilla exists don't realize it's also for feature requests.
    - The people who know bugzilla exists don't realize they can "vote" for desired features.
    - The voting system is "hidden" in bugzilla and unless you're really looking for it, most people don't notice it.
    - Do you really think the average person reads through every feature request and figures out if they want to vote for it?

    In other words, I don't believe the feature request system or the voting system work very well. Only a small minority of people who visit the forums to request a feature will actually figure out they have to submit it into bugzilla and then do that. And of those people, even fewer will bother to search out existing bugs/features and vote for them.

    If you really want to know what features are desired by your customers, then you should consider a different method of tracking feature requests and "voting".

    ie: Every month, cpanel devs could pick 10 features from the bugzilla list. Then they create a simple survey/voting page and send the link to all your customers, and also post it prominently here in the forums. Each feature in the list will link back to bugzilla (so people can see the details), and explain how to register for a bugzilla account and how the voting works. Basically, you are just "pointing" people to bugzilla with a bit of explaination and asking them to participate.

    I guarantee you will then get a much higher response, and people will feel like we are actually contributing something to cpanel.

    Repeat this every month, and before too many months, almost all your customers will know about bugzilla, that it can also be used for feature requests, and how the voting system works.

    Just my 2 cents.
     
    #8 electric, Nov 19, 2007
    Last edited: Nov 19, 2007
  9. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    You can look at my previous posts to verify the following:
    - When a feature is recommended on these forums, I typically follow-up with either an existing feature request that I instruct users can be voted upon or they can CC themselves for updates - or I recommend they submit it to http://bugzilla.cpanel.net and paste a link to their request to the forums so others know about and can vote and add themselves as CC on it.
    - Some people believe bugzilla is for direct customers only. When this is expressed on the forums or in a ticket, I kindly explain that the system is open to anyone who interacts with cPanel/WHM software

    The QA staff does review every bugzilla request (one that was entered when I began writing this post is already on our internal systems to be worked upon) and the Devs and QA inform people when functionality has been added.

    If you believe that is insufficient, let us know.

    Bugzilla as a software application isn't the greatest and the QA staff doesn't hold any punches about that :). I agree that the voting system isn't obviated in Bugzilla's interface. We do get many feature requests to Bugzilla itself, however those may be better addressed by the folks that make Bugzilla.

    I, personally, don't expect people to do what I do which is to periodically scan the entire list of open bugzilla requests. However, I think if people are on a forum topic all agreeing that a specific functionality would be a great addition to cPanel - that would be the best time to express such interest, because when customers/sysAdmins get distracted by their daily tasks and one day we pop up with that feature, they're happy to see it. Saying it's awesome today, but putting off commenting, CC'ing or voting till tomorrow - you may not remember tomorrow why this was such a great feature because you're focused on some other task.

    As for your suggestion of 10 new features a month, I don't think certain customers would like waiting the better part of a month before we go ahead with something like an updated PHP implementation or other rather pertinent functionalities. The bugzilla environment is conducive to being a fluid environment where the developers can easily gather public input and interpret it as they see fit. For example, in the past PHP feature requests on Bugzilla for new versions have been very active with dozens of votes and CCs and commentary to go along with that. As you can see now, turnaround time on PHP versions being implemented into EasyApache has substantially improved compared to even a year ago. I only discussed PHP versions because I know it's a frequent topic of discussion on Bugzilla, however the same could hold true about any feature request.
     
  10. electric

    electric Well-Known Member

    Joined:
    Nov 5, 2001
    Messages:
    697
    Likes Received:
    1
    Trophy Points:
    18
    Now you're just being sarcastic. :rolleyes:

    All I can say is that I personally feel there are a lot more people who don't know anything about bugzilla feature request voting system then there are people who do know about it.

    If you/cpanel feels things are ok how they are, then that's up to you/them. I'm only one person, just stating my opinion.

    The best thing I can do is recommend you judge and see things for yourself to determine if the current system is working. Go to bugzilla and pull some metrics off the voting system. What is the ratio of number of people registered in bugzilla against number of votes? If every person gets 5 votes, then there should be 5x as many votes as number of users.

    If you find this number is lower, then it means people are not using the voting system. You can then decide what changes, if any, are needed to "fix" that problem (assuming you feel it's a problem.)

    I also maintain my opinion that the current system is not intuitive. This most likely means you are losing out on a significant number of good features/suggestions from both customers and non-customers. Why do I say this? If a system is difficult to figure out, then you automatically are restricting the system to people "smart enough" (or who care enough) to figure it out. Are those the people you want to have in the system? Or do you also want the people who don't have time/patience/whatever to registrer in bugzilla, figure out the feature submission, voting, etc...

    Anyway, this is all just about usability.

    Cheers!
     
    #10 electric, Nov 19, 2007
    Last edited: Nov 19, 2007
  11. gtgeorge

    gtgeorge Well-Known Member

    Joined:
    Feb 28, 2007
    Messages:
    86
    Likes Received:
    0
    Trophy Points:
    6
    Yes I agree there should be a better request system in place. A forum where users can do nothing but feature requests would even be better in my opinion as I have seen it work nicely for other softwares. And then it could be monitored and passed along.
     
  12. cPanelBilly

    cPanelBilly Guest

    This is only an issue on Apache .1x, 2.2 shows the IP and not the domain name. If you do not want the domain name shown then update to Apache 2.2
     
  13. rustelekom

    rustelekom Well-Known Member
    PartnerNOC

    Joined:
    Nov 13, 2003
    Messages:
    290
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    moscow
    I learn bugzilla records and i need to day that it is not only reseller problem. It is most common problem. Host and reseller should have ability to manage which domain they want place as first on shared main ip. Let's say if i am a host and i want when visitor type server main shared ip in browser address window he become to my own site and not to the site which randomly selected by Cpanel. Early that was easy. I just need to place required site (virtual host section) right after correct ip and that's all. Now it is a problem because cpanel regenerate httpd config. I think will be very useful if somewhere in Cpanel we can stick required domain as "first" on shared ip's.
     
Loading...

Share This Page