Tranquil IT Forum

Published: **September 6, 2022 - 3:57 PM**

Good morning,

So here's the configuration:

* WAPT Server version: 2.2.2 (precision nightly 2.2.212405)
WAPT Agent version: 2.2.2.12388
WAPT Setup version: 2.2.2.12388
WAPT Deploy version: 2.2.2.12388
Discovery edition

* Debian Buster server operating system
* Windows 10 administration machine operating system

So, following an update from version 1.8.2 to 2.2.2 yesterday, for which I initially had a console login issue that was resolved thanks to the forum: viewtopic.php?t=3165

I have the workstations this morning that upgraded their agent to 2.2.2, except that the agents are not seeing any package updates (everything is OK even though it isn't)
And I see that my local repository is nowhere to be found. (error 404 not found). I'd rather ask you where to look before messing up my configuration

FYI, the wapt-get.ini file on the server is completely empty (just [global] written on line 1)
My wapt-get.ini file in c:\wapt has: repo_url=https://server_ip/wapt (results in a 404 not found error)

But from the local wapt page, the Repository/local repository link shows: http://server_ip/store (resulting in a 403 Forbidden error)

I imagine the URL changed with update 2.2.2?

Otherwise, just in case, I wanted to regenerate a package but it was impossible because:

: Capture.PNG (4.74 KB) Viewed 3200 times

the top of my www folder too:

Code: Select all

root@wapt:~# ls -la /var/www/
total 96
drwxr-xr-x 12 www-data www-data  4096 sept.  5 10:05 .
drwxr-xr-x 12 root     root      4096 mars  20  2017 ..
drwxr-xr-x  2 wapt     www-data  4096 avril 19  2018 html
-rw-r-----  1 wapt     www-data     0 sept.  5 10:05 licences.json
-rw-r--r--  1 wapt     www-data    26 sept.  5 12:26 robots.txt
-rw-r-----  1 wapt     www-data     0 déc.  14  2020 rules.json
drwxr-x---  2 wapt     www-data  4096 août  22  2019 ssl
-rw-r-----  1 wapt     www-data     0 déc.  14  2020 sync.json
drwxr-xr-x  5 wapt     www-data  4096 sept.  5 12:30 wads
drwxr-xr--  4 wapt     www-data 12288 sept.  5 12:30 wapt
drwxr-xr--  2 wapt     www-data  4096 mars  20  2017 waptdev
drwxr-xr--  2 wapt     www-data  4096 déc.  14  2020 wapt-diff-repos
drwxr-xr--  2 wapt     www-data  4096 mars  20  2017 wapt-group
drwxr-xr--  3 wapt     www-data 36864 sept.  5 14:05 wapt-host
drwxr-xr--  2 wapt     www-data  4096 avril 19  2018 wapt-hostref
drwxr-xr--  2 wapt     www-data  4096 mars  20  2017 waptwua

Thanks in advance !

Published: **September 8, 2022 - 4:40 PM**

Hello security_error,

security_error wrote: ↑September 6, 2022 - 3:57 PM So, following an update from version 1.8.2 to 2.2 yesterday, I initially had a console login issue which was resolved thanks to the forum: viewtopic.php?t=3165

OK

I did have the workstations this morning that upgraded their agents to 2.2.2, but the agents aren't seeing any package updates (everything appears OK even though it isn't).
Consequently, I see that my local repository is missing (error 404 not found). I'd prefer to ask where to look before messing up my configuration.

For your information, the wapt-get.ini file on the server is completely empty (just [global] written on line 1).

wapt-get.ini is for the agent; it is not essential to have the agent on the server.

My wapt-get.ini file in c:\wapt has: repo_url=https://server_ip/wapt (results in a 404 Not Found error).

However, from the local wapt page, the Repository/local repository link returns: http://server_ip/store (results in a 403 Forbidden error).

The repository URL should be like the one below; it's strange that it worked with the /store URL...

Code: Select all

http://serveur_ip/wapt

Otherwise, just in case, I wanted to regenerate a package but it was impossible because:

You need to update waptsetup.exe on the management machine to generate a new agent.

Sincerely,

Denis

Published: **September 20, 2022 - 3:13 PM**

Okay, just to wrap things up, faced with the deluge of errors visible in the various log files, I reinstalled Debian 11 and Wapt over it.

Things are working again; I just made sure to keep my c:\private folder with the keys, which I then used to re-sign the packages.
I just had to reconfigure and apply the groups afterward.

Published: **September 22, 2022 - 09:05**

Thanks for the feedback, I'm closing the topic

Tranquil IT Forum

[RESOLVED] No longer able to access local repository after update

[RESOLVED] No longer able to access local repository after update

Re: No longer accessing local repository after update

Re: No longer accessing local repository after update

Re: No longer accessing local repository after update