Log retention period for problematic logs

[ceceu08]

I'm having trouble with the log retention period for my users.

The period is set to 30 days as shown in the image.


But when I try to go back beyond 48 hours, it doesn't show me anything for any user. How can I solve this?

[support200]

Show me /nxfilter/log/nxfilte.log file. We need to see how many requests you get first.

[ceceu08]

Show me /nxfilter/log/nxfilte.log file. We need to see how many requests you get first.

There are many files; which one do you want to view?

[ceceu08]

Is this attached document sufficient?

[support200]

I don't think you have too many queries. What's the version? The current version is v4.7.4.3. If you use an older version, you'd better update it first.

You also can use the new GUI. https://tutorial.nxfilter.org/doc/en/h-sandwatch.php

[ceceu08]

I don't think you have too many queries. What's the version? The current version is v4.7.4.3. If you use an older version, you'd better update it first.

You also can use the new GUI. https://tutorial.nxfilter.org/doc/en/h-sandwatch.php

My version is 4.3.8.7

Do you think it's better to update to the latest version since I can't see page history for pages accessed more than 48 hours ago?

[support200]

Generally speaking, it's better to update to the newest version to eliminate other possibilities. And we only can fix the newest version anyway.

I guess the source of the problem is the Fetch Limit we have in the webpage. We still have it for the new GUI. However, you can increase it in the search tab. So, you can try the new one and then talk to us again.

[ceceu08]

Generally speaking, it's better to update to the newest version to eliminate other possibilities. And we only can fix the newest version anyway.

I guess the source of the problem is the Fetch Limit we have in the webpage. We still have it for the new GUI. However, you can increase it in the search tab. So, you can try the new one and then talk to us again.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
It was not possible to update the NxFilter XXX version (Datacomex version) to a new updated version.


The procedure performed for the update:

Downloaded the file with the latest version of Nxfilter
Installed the .deb package on the Nxfilter server
Updated with the dpkg command

After successful update, the program starts, and when it tries to update the Nxfilter database, it gives an error and the Nxfilter service crashes.

A backup was also performed via the web panel, and the file was extracted and stored in the /nxfilter/db folder, but the same problem occurred, the service starts and then gives an error.

Attached is a screenshot of the error.

-----------------------------------------------------------------------------------------------------------------------------------

[support200]

What's Datacomex version? If you send me the config db in /nxfilter/db or the backup file from System > Backup I can test it.

[support200]

Send config.db.h3 or the backup file to support @ nxfilter.org

[ceceu08]

What's Datacomex version? If you send me the config db in /nxfilter/db or the backup file from System > Backup I can test it.

The version we are running is 4.3.8.7, and we are trying to update to the latest version.

[ceceu08]

Send config.db.h3 or the backup file to support @ nxfilter.org

I am emailing it to you right now.

[support200]

I tried to update it on my system. It updtaes without any problem. I have sent you the updated config db file. Try it.

[ceceu08]

I tried to update it on my system. It updtaes without any problem. I have sent you the updated config db file. Try it.

I’ve now updated to the latest version of NXFilter (4.7.5.4), but I’m facing a different issue.

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?

[support200]

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:

nslookup porn.com 127.0.0.1

If you blocked 'porn.com', you will get your server IP as the response.