{"result":{"depiction_url":null,"edges":{"references":{"objects":[{"created":"2020-05-30T05:47:48Z","object_id":{"id":1990,"is_a":["text","documentation","developerguide"],"name":"doc_developerguide_deployment_varnish","title":"Using Varnish as frontend for Zotonic","uri":"https:\/\/zotonic.com\/id\/1990"},"seq":1000000},{"created":"2020-05-30T05:47:48Z","object_id":{"id":1790,"is_a":["text","documentation","developerguide"],"name":"doc_developerguide_deployment_nginx","title":"Proxying Zotonic with nginx","uri":"https:\/\/zotonic.com\/id\/1790"},"seq":1000000}],"predicate":{"id":332,"is_a":["meta","predicate"],"name":"references","title":{"_type":"trans","tr":{"en":"References"}},"uri":"https:\/\/zotonic.com\/id\/references"}},"relation":{"objects":[{"created":"2020-05-30T05:47:48Z","object_id":{"id":1279,"is_a":["text","documentation"],"name":"doc_glossary","title":"Glossary","uri":"https:\/\/zotonic.com\/id\/1279"},"seq":1000000}],"predicate":{"id":303,"is_a":["meta","predicate"],"name":"relation","title":{"_type":"trans","tr":{"nl":"Relatie","en":"Relation"}},"uri":"http:\/\/purl.org\/dc\/terms\/relation"}}},"id":1789,"is_a":["text","documentation","developerguide"],"links":[{"rel":"self","target":"https:\/\/zotonic.com\/.zotonic\/websub\/topic\/1789"},{"rel":"hub","target":"https:\/\/zotonic.com\/.zotonic\/websub"}],"medium":null,"medium_url":null,"name":"doc_developerguide_deployment_privilegedports","page_url":{"en":"https:\/\/zotonic.com\/docs\/1789\/running-on-port-80-and-port-443","x-default":"https:\/\/zotonic.com\/docs\/1789\/running-on-port-80-and-port-443"},"preview_url":null,"resource":{"version":20,"pivot_location_lat":null,"title":{"_type":"trans","tr":{"en":"Running on Port 80 and Port 443"}},"is_authoritative":true,"body":{"_type":"trans","tr":{"en":"
\n
\n

Using standard ports helps visitors discover your page and removes the awkward port number from URLs.<\/p>\n

The HTTP and HTTPS protocols are normally served on TCP ports 80 and 443. It is beneficial to run a these services on those standard ports: it aids discovery and lends a air of polish while a non-standard port number suggests something is incomplete.<\/p>\n

*nix systems only allow the superuser (root) to bind to ports below 1024. HTTP & HTTPS use ports 80 & 443 respectively. So setting up Zotonic to serve from those ports without running as superuser presents a problem, as *nix considers all ports below 1024 to be “privileged”, requiring special access.<\/p>\n

Other webservers (like nginx) typically do not have this problem, as they usually run their main unix process as root, but forking off child processes as non-privileged workers. Zotonic cannot be made to work like that because it is just one unix process, and running Zotonic entirely as the root user is considered harmful.<\/p>\n

This manual outlines three different methods to let Zotonic listen on port 80. All of them are for *nix based systems only.<\/p>\n

\n

Pre-launch notes<\/h2>\n

Before Zotonic serves its sites on a privileged ports, the hostname portions of your Zotonic sites need to be changed to reflect this.<\/p>\n

For production release of your new Zotonic site you need to:<\/p>\n