If the user is deploying docuseal behind an existing reverse proxy (nginx) there are certain headers that need to be set in order for the application to correctly function.
If the headers are not present the user will receive a 422 error page, and will see the following in the logs
ActionController::InvalidAuthenticityToken (HTTP Origin header (https://docuseal.mydomain.com) didn't match request.base_url (http://docuseal.mydomain.com)):
For nginx the following configuration is required in order for CORs to function properly.
If the user is deploying docuseal behind an existing reverse proxy (nginx) there are certain headers that need to be set in order for the application to correctly function.
If the headers are not present the user will receive a 422 error page, and will see the following in the logs
ActionController::InvalidAuthenticityToken (HTTP Origin header (https://docuseal.mydomain.com) didn't match request.base_url (http://docuseal.mydomain.com)):
For nginx the following configuration is required in order for CORs to function properly.