[SOLVED] Secondary respository (linux) Error 403 Forbidden

Share your tips or issues concerning the WAPT Console or WAPT Agent here
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
leduf63
Messages: 2
Registration: January 15, 2026 - 08:48

January 15, 2026 - 09:10

Hello,

Happy New Year 2026 everyone!

Our secondary WAPT repository (Linux Debian 13) has been working since January 6, 2026, but now it's causing "error 403 Forbidden" errors (in the WAPT console).
Do you have any idea what might be causing this?

In the Nginx server logs (error.log), I have many entries for: 13 permission denied
leduf63
Messages: 2
Registration: January 15, 2026 - 08:48

January 15, 2026 - 4:41 PM

Actually, I found the problem: the /opt folder had changed its Unix permissions to 700... I changed them back to 755 and everything is working perfectly again.
Weird.
User avatar
dcardon
WAPT Expert
Messages: 1929
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

January 16, 2026 - 6:11 PM

Good evening leduf63,

thank you for the feedback. :-)

I don't see a case where the Wapt agent itself could perform a chmod 700 /opt; either there was a mistake, or there's a poorly formatted Wapt package. :-)

I'm marking the topic as resolved.

Regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Locked