jermcel
-
Posts
11 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by jermcel
-
-
Okay...I have resolved this issue finally. It is always something small.
In my ovpn file I have several remote access points that allow port forwarding
******
remote ca-toronto.privacy.network 1198
remote ca-montreal.privacy.network 1198
remote ca-vancouver.privacy.network 1198
remote de-berlin.privacy.network 1198
remote de-frankfurt.privacy.network 1198
remote france.privacy.network 1198
remote czech.privacy.network 1198
remote ro.privacy.network 1198************
I did this incase an endpoint goes down that it would go to the next one.
I did a double check against PIA servers again for port forward enabled endpoints using this Curl command.
curl.exe -s https://serverlist.piaservers.net/vpninfo/servers/v6 | head -n1 | jq -r '.regions | .[] | select(.port_forward) | .name' | sort
I checked the results against my ovpn list and it appears that Spain was removed from the port forward enabled endpoints.
So the lesson learned here is that if your ovpn file has multiple endpoints and one of those is removed from the list in PIA, it will not connect correctly. Once I removed Spain, it connected just fine.
-
-
1 hour ago, binhex said:
set STRICT_PORT_FORWARD to 'no' if you do not want an incoming port or switch to one of the endpoints listed in the log that does support port forwarding.
This is going to sound dumb, but here goes. I am looking in the supervisord.log but I don't know where the "list" of approved items are at. It is only showing "Info" level logs and I am not sure where to find this or how to elevate the supervisord.log to be verbose. Am I looking in the wrong spot? I tried setting the config for Debug to true, but that does not increase or provide the info in the log either.
-
On 7/26/2024 at 8:23 AM, jermcel said:
Having issues with PIA Port Forwarding OVPN's. They just stopped working in the last few days and I don't know why. I was using CA Toronto.
I queried the API to get valid port forward endpoints using the following:
$ curl -s https://serverlist.piaservers.net/vpninfo/servers/v6 | head -n1 | jq -r '.regions | .[] | select(.port_forward) | .name' | sort
I have tried every other Canada endpoint as well as Netherlands, Berlin and Mexico, but I get this in the log each time.
2024-07-26 08:11:36,228 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port for 'pia'
[info] Port forwarding is enabled
[info] Checking endpoint 'de-berlin.privacy.network' is port forward enabled...2024-07-26 08:11:37,275 DEBG 'start-script' stdout output:
[info] PIA endpoint 'de-berlin.privacy.network' is NOT in the list of endpoints that support port forwarding shown below:-2024-07-26 08:11:38,324 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] Script finished to assign incoming portAm I missing something that has changed at PIA? Can someone point me in the right direction?
Bumping this. I still have not resolved this issue and I am not sure what the problem is. Can someone point me in the right direction. Regardless of what PIA endpoint I choose, DelugeVPN says it is not in the list of endpoints that support port forwarding.
-
Having issues with PIA Port Forwarding OVPN's. They just stopped working in the last few days and I don't know why. I was using CA Toronto.
I queried the API to get valid port forward endpoints using the following:
$ curl -s https://serverlist.piaservers.net/vpninfo/servers/v6 | head -n1 | jq -r '.regions | .[] | select(.port_forward) | .name' | sort
I have tried every other Canada endpoint as well as Netherlands, Berlin and Mexico, but I get this in the log each time.
2024-07-26 08:11:36,228 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port for 'pia'
[info] Port forwarding is enabled
[info] Checking endpoint 'de-berlin.privacy.network' is port forward enabled...2024-07-26 08:11:37,275 DEBG 'start-script' stdout output:
[info] PIA endpoint 'de-berlin.privacy.network' is NOT in the list of endpoints that support port forwarding shown below:-2024-07-26 08:11:38,324 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] Script finished to assign incoming portAm I missing something that has changed at PIA? Can someone point me in the right direction?
-
I am also having an issue of Unmountable: Wrong or no file system on Disk2 of my array. Currently, it is being emulated, but regardless of what I have tried it will not mount.. I attaching my diagnostics on here if someone is able to read and understand what is going on I would appreciate it.
Regards,
JC
-
On 9/21/2017 at 8:03 AM, jermcel said:
I have a question that may have been answered somewhere before but I cannot find it in a search. I am running the UniFi docker in Unraid and it works great. However, I need to create a config.gateway.json file and put it in the /data/sites/ directory. I cannot find this directory anywhere. There should be a /maps directory in the /sites directory.
What I am trying to accomplish is to put a Unifi Security Gateway (USG) in pass-through mode. In order to do this in with persistance, you have to add the .json file to the controller and it is provisioned to the USG. Otherwise, the USG will revert every time it is updated. There is no way thru the UI to do this yet.
This is the link to describe what I am doing.
Can someone please provide steps to find and access this directory
Regards,
JC
Can anyone comment on this. I am still not able to find the sites directory on this.
Regards,
JC
-
I have a question that may have been answered somewhere before but I cannot find it in a search. I am running the UniFi docker in Unraid and it works great. However, I need to create a config.gateway.json file and put it in the /data/sites/ directory. I cannot find this directory anywhere. There should be a /maps directory in the /sites directory.
What I am trying to accomplish is to put a Unifi Security Gateway (USG) in pass-through mode. In order to do this in with persistance, you have to add the .json file to the controller and it is provisioned to the USG. Otherwise, the USG will revert every time it is updated. There is no way thru the UI to do this yet.
This is the link to describe what I am doing.
Can someone please provide steps to find and access this directory
Regards,
JC
[Support] binhex - DelugeVPN
in Docker Containers
Posted
I did not remove them.
That was my issue...it was not showing the list on the failure, but did show them when it connected