Page 1 of 1
WAPT agent behind a NAT
Published: August 2, 2017 - 11:10
by neckatskin
Hello,
As I read in the documentation, the WAPT server cannot directly contact the WAPT agent behind a NAT. You mentioned that this problem can be bypassed soon using WebSocket. Do you have any indication of when this update will be released to address this issue? Is there a workaround in the meantime (VPN or other)?
Thank you in advance for your reply,
NeckAtSkin
Re: WAPT agent behind a NAT
Published: August 2, 2017 - 12:00 PM
by sfonteneau
Hello,
version 1.5 is in production here and working, however, the migration from 1.3.13 to 1.5 is not ready (at all).
For your information, version 1.5 of Wapt is currently not functional with a Windows server.
Only the Linux version works correctly. We have many changes to make for the new version to work under Windows.
We mainly need to adapt Nginx and PostgreSQL for Windows.
Therefore, this requires quite a bit of work.
To answer your question, a VPN solves this problem without any issues.
Simon
Re: WAPT agent behind a NAT
Published: August 2, 2017 - 12:23
by neckatskin
Okay, great. Thank you for your reply

Re: WAPT agent behind a NAT
Published: January 5, 2018 - 5:48 PM
by link6
Hello,
do you have any updates regarding this issue since last summer?
Do you know when the next version will be available?
Thanks in advance!
Sébastien
Re: WAPT agent behind a NAT
Published: January 5, 2018 - 9:31 PM
by sfonteneau
Hello,
documentation has just been published for migrating from version 1.3 to 1.5:
viewtopic.php?f=13&t=826&start=20.
It is strongly recommended that if you are coming from a Windows server, you migrate to a Linux server for this migration to 1.5.
This version is in Release Candidate (RC), so you can already do some testing!
Simon