cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
17,470
2,843
363
cPanel Access Level
Root Administrator

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
17,470
2,843
363
cPanel Access Level
Root Administrator
There shoudn't be, no.

As an example, when a cPanel user installs nginx, we setup an internal proxy. Nginx listens publicly on ports 80 and 443, but the Apache configuration is updated to use ports 81 and 444 so it can still delivery unsecured and secured content. As long as the port you're forwarding to is something that is listening for https connections, I'd expect that to work.

If the port is a different service, there may need to be some manual configuration to ensure Apache can still deliver an SSL.
 
Mar 28, 2023
15
1
3
Canada
cPanel Access Level
Root Administrator
Error Logs:
'
[Fri Mar 31 08:06:30.776104 2023] [autoindex:error] [pid 13911:tid 47315928778496] [client [MY IP]] AH01276: Cannot serve directory /home/[USER]/public_html/[SUBDOMAIN]/: No matching DirectoryIndex (index.php,index.php8,index.php7,index.php5,index.perl,index.pl,index.plx,index.ppl,index.cgi,index.jsp,index.jp,index.phtml,index.shtml,index.xhtml,index.html,index.htm,index.js) found, and server-generated dir$
[Fri Mar 31 08:06:30.776462 2023] [core:error] [pid 13911:tid 47315928778496] [client [MY IP] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
'
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
17,470
2,843
363
cPanel Access Level
Root Administrator
The web content is still served from the same location, so all your normal web files would need to be at that location, or you'll need to specify an alternative index page using the .htaccess file and the DirectoryIndex directive.