Our infrastructure consists of a .NET back-end, an Angular 5 application, and a nginx server. Upon registering your account in the application, you will receive an email with a verification link structured as follows:
[root]/register/verify?userId=blabla&code=blabla
Clicking on this link should direct you to the Angular app, but instead, it results in a nginx 404 error page being displayed.
However, if you first navigate to the index page [root]
, allowing the Angular app to start, and then manually append the verification link
/register/verify?userId=blabla&code=blabla
, it functions properly - the service is called, and the email is verified.
It appears that the issue arises when attempting to access the application from an external source, causing nginx to struggle processing the URL. I have attempted various adjustments on the Angular side, following advice offered in this answer without achieving any success.
I believe the solution lies within adjusting certain nginx settings. Can anyone confirm this assumption, and provide guidance on what changes need to be made in order for this configuration to function correctly?