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
WAPT agent behind a NAT
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
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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
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
-
neckatskin
- Messages: 14
- Registration: June 19, 2017 - 4:24 PM
Okay, great. Thank you for your reply 
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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
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
