Option to enable 444 on default site and access list

[axiom00]

Would it be possible to add a fifth option on the default site configuration to return 444 connection dropped? Also nice to have the 444 option as a toggle in the access list Deny All rule instead of the current 403.

Thanks.

[brtwrst]

I have the same "Issue"/Wish.
You can work around it a little bit.

1. Go to settings and select 404 Page as Default Site
2. SSH into your machine and go to [npm_data_volume]/nginx/default_host/site.conf and change the 404 to 444 in that file.

This change will persist until you select a new option for the Default Site.

[webartifex]

Just saw this issue and want to encourage that the above suggestions become features eventually.

I work with the exact same fixes, but having them as GUI options for not so "tech" savvy people would probably be great.

[LaazV]

Yes, please! Been wanting this for a while since I'm using a wildcard dns entry, and don't want the server responding to any subdomain.

Maybe even a 6th option "Custom Nginx Configuration" to allow for other edge cases when needed.

[KGBist2000]

yes please, return code 444 is much safer, than 404.
One of the usecase is when somebody try to connect via IP and not via hostname/domainname to close the connection by 444 and do not return any information about the server.

[tomassanjuann]

Up for this. Custom HTTP codes are an improvement in my opinion.

[github-actions]

Issue is now considered stale. If you want to keep it open, please comment 👍