ea-Nginx configurations that don't get overwritten

servtastic

Member
Sep 3, 2020
19
2
3
USA
cPanel Access Level
Root Administrator
Hi,

I am testing ea-nginx on Centos7 / cp94 (I have to have php56) and am running into a set of issues.

Main one for now, is setting configurations that work and do not get overwritten

Configs:
include rocket-nginx/default.conf;
listen 443 ssl http2;

If I put these in the users/[account].conf then both work, but they get overwritten.

I've tried editing different files in /etc/nginx and have also tried custom conf files, but no other file, other than users conf file, works.
Ideally, these two configs would be set for all accounts.

Suggestions?
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
7,519
1,030
313
cPanel Access Level
Root Administrator
Hey there! The best documentation I have available on this is here:


under the "Custom Configurations" section. There are details there for both global and individual server blocks. Can you check that out and see if that helps?
 

servtastic

Member
Sep 3, 2020
19
2
3
USA
cPanel Access Level
Root Administrator
Hi,

Yes, I have read that section - it's a bit thin.

1.
I have managed to get "include rocket-nginx/default.conf;" working, but it means I have to manually create a new folder and conf file for every website
I've tried to make this config global but it either does not work (server-includes) or throws an error (in conf.d - [emerg] "set" directive is not allowed here in ...)
I must be missing a step in making this a global include

2.
I cannot seem to overload listen with http2 - so get an error everywhere, except in the generated user conf file
Again, there must be a way to turn on http2 globally, but I have not found it yet.

So far I have one clunky solution and am stuck on adding the second :(
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
7,519
1,030
313
cPanel Access Level
Root Administrator
For issue 1, it sounds like this is more of a configuration issue if you're getting errors.

2 - This isn't fully supported at this time. There's some more discussion on this here:


Feel free to open a ticket with our team so we can check out the configuration issues. Just post the ticket number here once you've done that so I can make sure this thread stays updated.