Unfortunately, there's no domain on these machines.
I'll run my tests when the new version is available.
Thanks again for your feedback and quick response.
The search returned 135 results
- June 16, 2021 - 2:02 PM
- Forum: WAPT Server
- Subject: [SOLVED] http_proxy: get() takes exactly 3 arguments (4 given)
- Answers: 8
- Views : 8520
- June 15, 2021 - 12:09
- Forum: WAPT Server
- Subject: [SOLVED] http_proxy: get() takes exactly 3 arguments (4 given)
- Answers: 8
- Views : 8520
Re: [SOLVED] http_proxy: get() takes exactly 3 arguments (4 given)
Thank you for your feedback and quick response regarding the fix in version 1.8.2.
Since my workstations are no longer reachable, is a manual update or one using another tool required? Is the fix not only server-side but also agent-side?
Since my workstations are no longer reachable, is a manual update or one using another tool required? Is the fix not only server-side but also agent-side?
- June 14, 2021 - 11:19
- Forum: WAPT Server
- Subject: [SOLVED] http_proxy: get() takes exactly 3 arguments (4 given)
- Answers: 8
- Views : 8520
Re: http_proxy: get() takes exactly 3 arguments (4 given)
Version with the problem:
WAPT Server version: 1.8.2
WAPT Agent version: 1.8.2.7334
Example version without the problem:
WAPT Server version: 1.8.2
WAPT Agent version: 1.5.1.26
WAPT Server version: 1.8.2
WAPT Agent version: 1.8.2.7334
Example version without the problem:
WAPT Server version: 1.8.2
WAPT Agent version: 1.5.1.26
- June 9, 2021 - 7:46 PM
- Forum: WAPT Server
- Subject: [SOLVED] http_proxy: get() takes exactly 3 arguments (4 given)
- Answers: 8
- Views : 8520
[SOLVED] http_proxy: get() takes exactly 3 arguments (4 given)
Hello,
we noticed today that all our workstations behind a proxy server were no longer communicating with the WAPT server.
After many hours of searching, it seems we've identified the problem.
The WAPT service was stopped on the workstations, displaying this error:
https://i.ibb ...
we noticed today that all our workstations behind a proxy server were no longer communicating with the WAPT server.
After many hours of searching, it seems we've identified the problem.
The WAPT service was stopped on the workstations, displaying this error:
https://i.ibb ...
- February 8, 2021 - 5:55 PM
- Forum: WAPT Server
- Subject: Internal Server Error - 'ascii' codec can't encode characters in position 0-32: ordinal not in range(128)
- Answers: 5
- Views : 8547
Re: Internal Server Error - 'ascii' codec can't encode characters in position 0-32: ordinal not in range(128)
Thank you for your feedback.
Do I need to patch and recompile the WAPT console? Or is there another way to do it?
Do I need to patch and recompile the WAPT console? Or is there another way to do it?
- February 3, 2021 - 4:33 PM
- Forum: WAPT Server
- Subject: Internal Server Error - 'ascii' codec can't encode characters in position 0-32: ordinal not in range(128)
- Answers: 5
- Views : 8547
Re: Internal Server Error - 'ascii' codec can't encode characters in position 0-32: ordinal not in range(128)
I'd like to bring this topic up again.
- January 20, 2021 - 2:21 PM
- Forum: WAPT Server
- Subject: Internal Server Error - 'ascii' codec can't encode characters in position 0-32: ordinal not in range(128)
- Answers: 5
- Views : 8547
Re: Internal Server Error - 'ascii' codec can't encode characters in position 0-32: ordinal not in range(128)
I'm just bumping this thread.
- November 19, 2020 - 11:45 AM
- Forum: WAPT Server
- Subject: Internal Server Error - 'ascii' codec can't encode characters in position 0-32: ordinal not in range(128)
- Answers: 5
- Views : 8547
Internal Server Error - 'ascii' codec can't encode characters in position 0-32: ordinal not in range(128)
Hello,
On a newly installed client machine, I'm getting an error when I try to access http://localhost:8088/.
Internal Server Error:
The server encountered an unexpected internal server error
(generated by waitress).
I noticed in the logs that there was an ASCII problem...
On a newly installed client machine, I'm getting an error when I try to access http://localhost:8088/.
Internal Server Error:
The server encountered an unexpected internal server error
(generated by waitress).
I noticed in the logs that there was an ASCII problem...
- December 10, 2018 - 5:06 PM
- Forum: WAPT Server
- Subject: WAPT server stops working
- Answers: 9
- Views : 13520
Re: WAPT server stops working
I'm bumping this thread; the problem persists and I don't have many leads...
WAPT Server version: 1.6.2.7
WAPT Server version: 1.6.2.7
- November 22, 2018 - 12:33
- Forum: WAPT Packages
- Subject: Website URL Shortcut
- Answers: 4
- Views : 7826
Re: Website URL Shortcut
Hello,
could you please post your package code so we can help you?
could you please post your package code so we can help you?
