Forwarded to devs 403 Forbidden wont go away

[MarkgWatson]

TITLE:

403 Forbidden wont go away​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Plesk Onyx
Version 17.8.11 Update #35
Ubuntu
Nginx
PHP - Laravel​

PROBLEM DESCRIPTION:

I setup a few subdirectory paths, following are two examples
https://www.topdestinations.link/country/south-america
https://www.topdestinations.link/country/asia

Which initially was returning a 403 forbidden.

I then fixed the problem where redirects would take the client to a default page. As you can see here the page will default.
Top Destinations

After asserting that it was not the PHP Framework forcing a 403, I then researched possible solutions I addressed advise to clear the nginx cache all though i am not sure where it is located. I have restarted nginx and even the server to see if it resolves. But it is still not able to reset the prior cached paths which will not stop resolving a 403.

I as well attempted to run this command 'plesk sbin httpdmng --reconfigure-all' nothing has changed the cache of the legacy 403 forbidden error still resolves.

As well in the panel nginx config of the domain I disabled the option Smart static files processing. This has not resolved problem either.

It truelly identifies that there is a cache problem, could you advise a work around that i may use in the interim until the bug is resolved please.​

STEPS TO REPRODUCE:

This will show a cache bug of a 403 error
Go here: https://www.topdestinations.link/country/south-america

This will show an updated application able to resolve
Go here:
Top Destinations​

ACTUAL RESULT:

403 Forbidden Response​

EXPECTED RESULT:

OK​

ANY ADDITIONAL INFORMATION:

​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Help with sorting out​

 

[SibProgrammer]

It doesn't look like a Plesk control panel problem.
It seems /country/south-america is a directory and there is no any file listed as DirectoryIndex. I mean the directory doesn't contain index.html or index.php or something similar.
Another reason of such problems can be .htaccess files with specific directives. You can try to remove to check if it's a root cause.