Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Paste contents of /etc/nginx/nginx.conf and /etc/nginx/conf.d/brotli.conf
Heya,
The error message says:
nginx: [emerg] unknown directive "brotli" in /etc/nginx/conf.d/brotli.conf:1
This means that NGINX does not recognize the brotli directive, which is used for Brotli compression. This can occur if the Brotli module is not installed or not properly configured in NGINX.
Here are some steps to solve this issue:
Check if the Brotli module is installed: The Brotli module is not included in the standard NGINX build, and you need to install it separately. You can do this by either compiling NGINX from the source with the Brotli module or installing it via a package manager if it’s available.
If the Brotli module is installed, check the NGINX configuration: Make sure that the Brotli module is correctly configured in your NGINX configuration files. It seems that your Brotli configuration is in /etc/nginx/conf.d/brotli.conf. You may want to check that file for any errors. If you don’t need Brotli compression, you could comment out the lines related to Brotli to stop the error from occurring.
Check the NGINX version: Ensure that your version of NGINX supports the Brotli module. You might need to upgrade NGINX to a newer version if the current version doesn’t support Brotli.
Test the NGINX configuration: After making changes to the configuration files, always run sudo nginx -t to test the configuration. This command will check your configuration for syntax errors and will help you find where the problem lies.
After you’ve resolved the issue, you can then restart NGINX with sudo systemctl restart nginx and it should start without any errors.
Remember to make backups of any configuration files before modifying them, as incorrect configurations can cause service disruptions.