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.

[Case 104349] 1:1 NAT Account Creation Discrepancy

Discussion in 'General Discussion' started by sparek-3, Jun 12, 2014.

  1. sparek-3

    sparek-3 Well-Known Member

    Joined:
    Aug 10, 2002
    Messages:
    1,382
    Likes Received:
    23
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    We have a provider that switched us to a set up that includes 1:1 NAT. We haev an Internet public facing IP address (204.x.x.x) that routes to a private IP address (10.x.x.x).

    I'm noticing a discrepancy in the way this works.

    When creating a new account in the WHM, the resulting page that shows the account being created shows:

    Code:
    WWWAcct 12.5.0 (c) 2014 cPanel, Inc....
    
    Dns Zone check is enabled.
    +===================================+
    | New Account Info                  |
    +===================================+
    | Domain: %domain%
    | Ip: 204.x.x.x (n)
    | HasCgi: y
    | UserName: %username%
    | PassWord: %password%
    | CpanelMod: x3
    | HomeRoot: /home
    | Quota: 500 Meg
    | NameServer1: %nameserver1%
    | NameServer2: %nameserver2%
    | NameServer3: 
    | NameServer4: 
    | Contact Email: 
    | Package: %package%
    | Feature List: default
    | Language: en
    +===================================+
    ...Done
    This would seem to be correct, at least this is what I would prefer it show. Note the Ip: that is listed.

    But the email message, the message you get when a new account is created in your Inbox shows:

    Code:
    Subject: New account on %server% (%domain%)
    +===================================+
    | New Account Info |
    +===================================+
    | Domain: %domain%
    | Ip: 10.x.x.x (n)
    | HasCgi: y
    | UserName: %username%
    | PassWord: %password%
    | CpanelMod: x3
    | HomeRoot: /home
    | Quota: 500 Meg
    | NameServer1: %nameserver1%
    | NameServer2: %nameserver2%
    | NameServer3:
    | NameServer4:
    | Contact Email:
    | Package: %package%
    | Feature List: default
    | Language: en
    +===================================+
    Account was setup by: root (root)
    Note that the Ip is different here, it is showing the private IP address.

    Is this the way this is suppose to work?

    I would prefer it if both messages showed the public facing IP, the 204.x.x.x IP. But either way, it would seem that there is a discrepancy here.
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,762
    Likes Received:
    662
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    Was NAT configured before cPanel was installed? Or, was it setup after the installation? If it was setup after the installation, you can try running the build_cpnat script:

    build_cpnat script

    Also, what IP address is configured as the main shared IP address in "WHM Home » Server Configuration » Basic cPanel & WHM Setup"?

    Thank you.
     
  3. sparek-3

    sparek-3 Well-Known Member

    Joined:
    Aug 10, 2002
    Messages:
    1,382
    Likes Received:
    23
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    It was setup after the installation. The datacenter, in their infinite wisdom, decided to move the service into this type of setup.

    I did run the build_cpnat script, otherwise the IPs for Apache and the DNS zones gets mismatched.

    A strange thing about the Main Server Shared IP Address is that it's set to the 204.x.x.x IP address, but /etc/wwwacct.conf is showing ADDR 10.x.x.x.

    Changing the Main Shared Server IP address (in Home > Server Configuration > Basic cPanel & WHM Setup) to the private IP 10.x.x.x and clicking Save Changes, reloading the page still shows the public IP address 204.x.x.x.

    But if you change the ADDR in /etc/wwwacct.conf to the public IP address, the emails works right, but the Apache configuration doesn't use the right IP.
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,762
    Likes Received:
    662
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    I believe this is by design, but it's likely a good idea to submit a bug report requesting the account creation email template matches the WHM creation result output. It's does not appear to result in any invalid configuration, but nonetheless you can submit a bug report for this behavior:

    Submit A Bug Report

    Please let us know the ticket number once you open the report.

    Thank you.
     
  5. cPanelToddR

    cPanelToddR Member
    Staff Member

    Joined:
    Oct 8, 2009
    Messages:
    21
    Likes Received:
    1
    Trophy Points:
    3
    Thanks for the report. This is clearly a bug. The internal case number is 104349
     
  6. sparek-3

    sparek-3 Well-Known Member

    Joined:
    Aug 10, 2002
    Messages:
    1,382
    Likes Received:
    23
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Thanks for this.

    No, as far as I can tell, it doesn't hamper functionality any. But, my main concern is resellers on this server, they may be using the email message as part of their welcome letter and they may be sending their new clients a welcome letter with the 10.x.x.x IP address, which won't get the end users anywhere.

    That's why I'd prefer the email to show the public facing IP, if it has to show one. But I thought something wasn't quite right anyway since the two messages weren't showing the same information.

    I did not mention this before, but this is on cPanel 11.42 (11.42.1.16 to be exact).
     
  7. cPanelToddR

    cPanelToddR Member
    Staff Member

    Joined:
    Oct 8, 2009
    Messages:
    21
    Likes Received:
    1
    Trophy Points:
    3
    Thanks for reporting this. The fix will be released with 11.44.1.x coming soon.
     
  8. sparek-3

    sparek-3 Well-Known Member

    Joined:
    Aug 10, 2002
    Messages:
    1,382
    Likes Received:
    23
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Any plans to push this out to 11.42? I usually stay the version behind the currently being developed version, due to stability. I always figured the older version (older, but still supported, 11.42 is still under support, isn't it?) would have most bugs (like this one) stamped out. Whereas 11.44 (or the currently developed version) would still have some details to iron out.
     
Loading...

Share This Page