Ngnix

Edit online

Issues and solutions related to Ngnix in Faspex 5.

Potential issue with external Ngnix and Faspex router

Because of changes in the Faspex router, customers with an external Nginx may encounter the WARN HTTP Origin header (https://domain.com:443) didn't match request.base_url (https:/domain.com/) error when using the external submission link for Shared inbox and personal invitations.

Workaround

Replace the line proxy_set_header Host $host:$server_port; with proxy_set_header Host $host; in your Nginx configuration. Restart both Nginx and Faspex after making this change.

Additional information

Changes in the Faspex router configuration:
  • New log format
  • New HTTP header: Added the proxy_set_header X-Forwarded-Server when Faspex router forwards a request to another server.
  • Redirection to HTTPS: Faspex router returns 302 https://$host:443$request_uri for requests reaching this configuration, they will be redirected to the HTTPS version of the same host and URI.
  • Asset forwarding: Request for assets are now forwarded to port 3000.