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.

cpanel redirection to https is malformed domain

Discussion in 'General Discussion' started by stardotstar, Sep 19, 2009.

  1. stardotstar

    stardotstar Well-Known Member

    Joined:
    Sep 14, 2009
    Messages:
    68
    Likes Received:
    0
    Trophy Points:
    6
    When first installed and I was playing around with the system (trial) the configuration of the server was

    jupiter.gnu.net.au

    on deployment I reconfigured it to

    jupiter.sourcepoint.com.au

    and changed that value everywhere I thought I had to.

    Now I see that redirection of a client from their virtual domain to the https is forming the old url/tld syntax

    ie if I am at

    Julie's Finger Food

    and I hit up

    http://www.juliesfingerfood.com.au/cpanel

    I get a redirection url that fails to resolve:

    https://jupiter.gnu.net.au:2083/

    The message is a page load error:
    Firefox can't find the server at jupiter.gnu.net.au.

    What have I failed to change or update such that the redirection of the site to the secure cpanel (as recommended in the firewall setup) can be done for the proper domain??

    Best regards,
    Will
     
  2. MattCurry

    MattCurry Well-Known Member

    Joined:
    Aug 18, 2009
    Messages:
    275
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Houston, Tx
    Hello,


    I do apologize that you are not able to get to that page. However, I was not able to replicate your problem. The page loads for me just fine, have you made sure and accepted the cert? This may depend on what browser you are using. Please try again and let me know if you still need our help.

    Thank you,
    Matthew Curry
     
  3. stardotstar

    stardotstar Well-Known Member

    Joined:
    Sep 14, 2009
    Messages:
    68
    Likes Received:
    0
    Trophy Points:
    6
    Thank you Matthew for your reply and no need to apologize! This must have been something to do with a latent dns issue I have been seeing on one other domain or as you suggest a cert thing at my browser end - it has evaporated for me too in the mean time. If I see it again I will report back but until then I believe it may have resolved itself.
    Will
     
Loading...

Share This Page