Tranquil IT Forum

I forgot to mention that for the "successful" installation, I had also completely uninstalled Kaspersky.

This isn't the first time Kaspersky has interfered with Wapt's operation. I'm starting to wonder if perhaps the file server version of Kaspersky would be better suited.

The password I was using contained a '', was only 9 characters long, and it crashed. So, during installation, I used "azerty". Then, I changed the passwords to a strong 10-character password.

Is it possible to run the Wapt repository over HTTP instead of HTTPS? Is this feature planned?

olivetree wrote: ↑May 24, 2018 - 5:29 PM
The password I was using contained << ' >>, was only 9 characters long, and it crashed. So during installation, I used "azerty". Then, I changed the passwords to a strong 10-character password.

Is it possible to run the WAPT repository over HTTP instead of HTTPS? Is this feature planned?

The password is already corrected; Hubert made the correction last night

https://github.com/tranquilit/WAPT/comm...ef6a3341b6

Using HTTP instead of HTTPS is already possible. You can even change the listening port. What's the goal, what's the problem? It's preferable to use HTTPS