<![CDATA[Persistent custom nginx configuration]]>I would find it very useful if i could enter custom nginx rules (generally or per application), that would survive updates. Is this possible at the time beeing?

]]>https://forum.cloudron.io/topic/8067/persistent-custom-nginx-configurationRSS for NodeFri, 07 Aug 2026 19:30:23 GMTWed, 23 Nov 2022 09:41:51 GMT60<![CDATA[Reply to Persistent custom nginx configuration on Mon, 28 Nov 2022 11:04:39 GMT]]>@opensourced said in Persistent custom nginx configuration:

plugins which are available for free are crapy and I dont trust them

fyi Wordfence is not crappy (imho everyone running WordPress should install it) and would easily sort this for you

]]>https://forum.cloudron.io/post/57223https://forum.cloudron.io/post/57223Mon, 28 Nov 2022 11:04:39 GMT<![CDATA[Reply to Persistent custom nginx configuration on Mon, 28 Nov 2022 10:07:06 GMT]]>@Latinosnctv Currently, adding custom nginx configs is not supported. I am not 100% sure, but if you use a WAF (like cloudflare), you can add rules there.

]]>https://forum.cloudron.io/post/57211https://forum.cloudron.io/post/57211Mon, 28 Nov 2022 10:07:06 GMT<![CDATA[Reply to Persistent custom nginx configuration on Sun, 27 Nov 2022 23:35:44 GMT]]>@nebulon Hello, I edited the nginx config manually on the server... to restrict access to chatwoot's super_admin url... but when I change the config in the app, everything added disappears

location ^~ /super_admin {
    allow 1.2.3.4;
    deny all;
    proxy_pass http://CHATWOOT_INTERNAL_INSTANCE_IP:3000;
}
]]>https://forum.cloudron.io/post/57192https://forum.cloudron.io/post/57192Sun, 27 Nov 2022 23:35:44 GMT<![CDATA[Reply to Persistent custom nginx configuration on Wed, 23 Nov 2022 10:47:17 GMT]]>@opensourced I think the WordPress issue can be solved with a htaccess file instead of doing this on a reverse proxy level https://docs.cloudron.io/apps/wordpress-developer/#htaccess

]]>https://forum.cloudron.io/post/56828https://forum.cloudron.io/post/56828Wed, 23 Nov 2022 10:47:17 GMT<![CDATA[Reply to Persistent custom nginx configuration on Wed, 23 Nov 2022 09:59:05 GMT]]>@nebulon See that point. Two use cases are:

WordPress exposes the example.com/xmlrpc.php API per default. We already had several issues where attackers used those APIs to send spam mails from our applications. To fix this issue, either you need to install a plugin that disables the API (however, dose plugins which are available for free are crapy and I dont trust them), or you just disable those requests in the nginx.conf of the application. This is what I did, but through updates those custom lines were deleted.

I would like to restrict the Synapse Admin API to certain IPs.

]]>https://forum.cloudron.io/post/56825https://forum.cloudron.io/post/56825Wed, 23 Nov 2022 09:59:05 GMT<![CDATA[Reply to Persistent custom nginx configuration on Wed, 23 Nov 2022 09:46:00 GMT]]>Generally we try to not expose such internals to the users, as they are inherently hard to test with regards to updates. Often though we can add a feature to "manage" such thing explicitly. What is the use-case for you and what would you like to add?

]]>https://forum.cloudron.io/post/56822https://forum.cloudron.io/post/56822Wed, 23 Nov 2022 09:46:00 GMT