Subdomain ports [Case 80225]

[fearlsgroove]

I use the tweak setting to change the apache port (to run behind varnish), and we often use subdomains. This used to work fine, but for the last week at least (hard to tell b/c we don't create them every day), the virtual hosts created by whm all use the standard port, disregarding the tweak settings.

Currently running WHM 11.40.0 (build 9)

 

[fearlsgroove]

Actually it looks like the custom apache port setting is just not working at all. New accounts also use the wrong port.

 

[cPanelMichael]

Hello

There is an internal case open to address this issue. For reference, the internal case number is 80225. The current workaround is to rebuild the Apache configuration file via:

/scripts/rebuildhttpdconf

You can monitor the cPanel Change Log for case 80225 to see when the resolution is released.

Thank you.

 

[kroko]

i'm using nginxcp and as a workaround i added the following lines at the end of /scripts/postwwwacct

the script was in python:

<code>
proc = subprocess.Popen("/usr/local/cpanel/bin/build_apache_conf > /dev/null 2>&1", shell=True)
output = proc.communicate()

proc = subprocess.Popen("/etc/init.d/httpd graceful > /dev/null 2>&1", shell=True)
output = proc.communicate()
</code>

 

[weetabix]

You can monitor the cPanel Change Log for case 80225 to see when the resolution is released.

Why is the log not updated? Shouldn't it be something new there now, since my build number is now WHM 11.40.0 (build 16)?

 

[cPanelMichael]

Why is the log not updated? Shouldn't it be something new there now, since my build number is now WHM 11.40.0 (build 16)?

The change log is now updated to reflect the newest build that has been pushed out. This includes a resolution for case 80225.

Thank you.

 

[weetabix]

The change log is now updated to reflect the newest build that has been pushed out. This includes a resolution for case 80225.

Thank you.

Good. =)

However, I am not seeing the changelog. The last build I see on that page is 11.40.0.9, am I doing something wrong or looking at the wrong place?

 

[cPanelMichael]

Try clearing your browser cache or trying from a different browser to ensure you the page you are viewing is not cached.

Thank you.