I don't know why your old version working but it can't connect the server.
ERROR [08-25 13:10:15] - NxPing.run, Connection error! IP = 212.38.89.xx
You'd need see if you can access your server first.
Announcement
Collapse
No announcement yet.
Log retention period for problematic logs
Collapse
X
-
See if the attachment helps us decipher the inconsistencies with version 1.3.1.Originally posted by support200 View PostYes. Zip the folder and send it to me.
Attached Files
Leave a comment:
-
It works fine on my system.
Look into the log file. Or post it here.
Leave a comment:
-
Originally posted by support200 View PostLocal Domain and Local DNS Server are for when you use it in your local network. I don't think there's much difference between v1.1.2 and v1.3.1.
Look into its log file first. It's in C:/Program Files (x86)/nxproxy/log directory. And run this command in CMD:
If you blocked 'porn.com', you will get your server IP as the response.Code:nslookup porn.com 127.0.0.1
Hello.
I am using NXPROXY agent version 1.1.2, and yes, I have pornographic content blocked.
But then why does my browsing work when I update to an agent version higher than 1.1.2?
Leave a comment:
-
Local Domain and Local DNS Server are for when you use it in your local network. I don't think there's much difference between v1.1.2 and v1.3.1.
Look into its log file first. It's in C:/Program Files (x86)/nxproxy/log directory. And run this command in CMD:
If you blocked 'porn.com', you will get your server IP as the response.Code:nslookup porn.com 127.0.0.1
Leave a comment:
-
I’ve now updated to the latest version of NXFilter (4.7.5.4), but I’m facing a different issue.Originally posted by support200 View PostI tried to update it on my system. It updtaes without any problem. I have sent you the updated config db file. Try it.
I can only use the NXProxy agent on version 1.1.2, not the latest version (1.3.1). I’ve noticed that when I update to the latest version and reboot the workstation, web browsing is intermittent—sometimes it works, sometimes it doesn't. Similarly, rule-based blocking works sometimes but not others. It seems like there’s an inconsistency with this latest version, or perhaps a configuration is missing on my server?
According to AI, the latest version of NXProxy requires some additional server-side configurations—such as pointing to the local DNS—but I’ve tried that without success. Do you have any tips or a solution?
Leave a comment:
-
I tried to update it on my system. It updtaes without any problem. I have sent you the updated config db file. Try it.
Leave a comment:
Leave a comment: