Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adguard and FTP connections #1864

Closed
3 tasks done
RebelliousX opened this issue Jan 23, 2024 · 1 comment
Closed
3 tasks done

Adguard and FTP connections #1864

RebelliousX opened this issue Jan 23, 2024 · 1 comment

Comments

@RebelliousX
Copy link

RebelliousX commented Jan 23, 2024

Please answer the following questions for yourself before submitting an issue.

  • I am running the latest version
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed

AdGuard version

4.4.35

Environment

- OS: Android 14
- Device: Z Fold 3

Issue Details

When I try to connect to my FTP/FTPS server through WAN, connection succeeds, but I don't get any files or folders listed.

Now, before you close this issue as won't fix. I am aware of the previous 2 issues: AdguardTeam/AdguardForAndroid#3835, and AdguardTeam/AdguardForAndroid#936.

The thing is, I tried to add the exclusion in Advanced low-level settings. But my problem is that I don't use an IP address to connect to the FTPS server. I created a Dynamic DNS from FreeDNS.afraid.org and another one from my Netgear router freely through no-ip.com

Something like:
subdomain.crabdance.com
subdomain.mynetgear.com

These URIs are reflecting my public IP from my ISP.

When I tired to enter these URIs into the exclusion list, Adguard complained that they are not
valid IP addresses.

For now, my only solution is to disable Adguard whenever I try to connect to my home's FTPS server
from WAN. The issue doesn't show up when I try to connect from LAN, since filtering for local IPs are disabled by default from the settings.

I don't want to put the IP address itself to be excluded, since that defeats the whole purpose of creating a Dynamic DNS in the first place. The IP address can change, but my DynamicDNS URIs should be permanent, and I would like to use these.

Shouldn't the external IP address of the host be excluded from filtering by default? I think to solve this issue and the previous closed issues is by doing that. And since the IP can change, Adguard should change that automatically too. And it is easy to get the external IP address anyways.

Anyway to fix this or a setting I am not aware of?
Thanks.

@Versty Versty transferred this issue from AdguardTeam/AdguardForAndroid Feb 26, 2024
@Versty
Copy link

Versty commented Feb 26, 2024

@RebelliousX Transferred to proper repository for further investigation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants