Announcement

Collapse
No announcement yet.

Nxcloud and Nxrelay

Collapse
X
Collapse
 
  • Page of 3
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 template Next
  • #16
    Did you restart it? Enable debugging on /nxrelay/conf/log4j.properties file by changing INFO to DEBUG and restart it again and then try to send some queries to NxRelay for those blocked domains and then show me your log in /nxrealy/log/nxrealy.log

    Those numbers are from some cache and we don't have operator level cache as it takes too much resource. There's still license counting and they will be warned if there are too many users for their license. And you can see their usage stats on Report > Operator Stats.

    Comment

    • #17
      I managed to make it work together with the Firewall, just one detail the IP that is not displayed and the IP of the user's machine behind the firewall is displayed the IP of the Firewall what could be happening?

      Comment

      • #18
        I managed to solve.
        The scope was as follows:

        Machine with NXrelay IP 172.16.1.50

        I configured Firewall to forward all DNS queries to this IP. In this way, all queries arrived with the Firewall IP in NXcloud.

        How to solve?
        Pointing the DNS delivered by the Firewall to the IP 172.16.1.50 (Machine with NXRelay).
        Last edited by Lenin; 08-09-2023, 11:10 PM.

        Comment

        • #19
          NxRelay needs to see your client IPs. Can it see the IPs?

          Comment

          • #20
            Yes, Nxrelay now brings the client's private IPs according to the user's association.

            My challenge now is to configure NXrelay with AD. If you can help me thank you.

            I'm having a conflict to start NXrelay in AD because AD already has DNS running on port 53.

            USr, java.net.BindException: Address already in use: Cannot bind
            Last edited by Lenin; 08-10-2023, 12:48 AM.

            Comment

            • #21
              Add one more IP to your Windows server and bind one DNS servers to one IP. https://tutorial.nxfilter.org/i-faq.php#bind-ip

              Comment

              • #22
                I don't understand how I'm going to add another IP in my AD, would you have any tutorial for that?

                Comment

                • #23
                  That's about Windows system. You can google it. Or watch this, https://www.youtube.com/watch?v=v2iI...nnel=Jahastech

                  Comment

                  • #24
                    I managed to perform the configuration with AD and everything seems to be fine.

                    I'm using cloudflare to protect access to the server with SSL however when I log in using the domain instead of the IP it seems to break the dashboard, the display of reports is infinitely loading.

                    What could be happening?

                    Comment

                    • #25
                      Did you block something for yourself by filtering? Otherwise, see if you have the same problem with our demo site.

                      Comment

                      • #26
                        The demo site works normally, this behavior only occurs when accessing through the Domain, if the access through the IP works normally.

                        In the demo I checked and I can access it also by IP and this breaks the SSL certificate.

                        Is it possible to block it so that it is not accessed by the IP address?

                        Comment

                        • #27
                          So, it works for https://demo.nxfilter.org? Then it's not SSL problem. It's more about domain resolving. Try oher DNS server while you access your site.

                          You can check SSL Only on 'System > Setup > Misc'. I guess it will block HTTP access for modern browsers. Or you could block TCP/80 on your firewall.
                          Last edited by support200; 08-11-2023, 03:45 AM.

                          Comment

                          • support200
                            #27.1
                            support200 commented
                            08-11-2023, 03:47 AM
                            Editing a comment
                            I was going to suggest webserver port change but it's not a good idea if you want to use some agents. Blocking TCP/80 also not a good idea.
                        • #28
                          And why do you try to bock TCP/80? Do you think it helps to your server protection? It only encrypts the traffic between browser and webserver. You may protect your password hijacked somewhere but you can use HTTPS always and modern browsers try to use HTTPS first always though it breaks a lot of thing in my opinion.

                          Comment

                          • Lenin
                            #28.5
                            Lenin commented
                            08-18-2023, 04:20 PM
                            Editing a comment
                            I performed a test with Mozilla Firefox and it is working ok.
                            Is it a bug with Edge and Chrome?
                          • support200
                            #28.6
                            support200 commented
                            08-18-2023, 04:20 PM
                            Editing a comment
                            And start a new thread with a new posting. That'd be better.
                          • support200
                            #28.7
                            support200 commented
                            08-18-2023, 04:29 PM
                            Editing a comment
                            I don't think so. Should be worknig with Edge and Chrome if it works with Firefox.
                        • #29
                          Dear All,

                          Am an MSP who would wish to test your product and see how it goes.

                          What are the prerequisites? Will I do my own hosting since am cloud service provider?

                          Thanks

                          Comment

                          • support200
                            #29.1
                            support200 commented
                            08-16-2023, 02:08 AM
                            Editing a comment
                            You need 2 servers on the cloud at least. Primary and secondary DNS servers for your users. You can run NxCloud in a cluster. NxCloud has a 30 day trial license included in its package.
                        • #30
                          Thanks for the response. What specs of servers would I need?

                          Comment

                          • support200
                            #30.1
                            support200 commented
                            08-16-2023, 07:23 AM
                            Editing a comment
                            No so much high spec. 6GB of RAM would be enough. You need to allocate 4GB to NxCloud. That'd be enough. 40GB of HDD but you would need to separate your logging/report server eventually if you deal with several thousands users. For CPU, I don't think it's too important. Even a CPU for PC would do the job.
                        Previous 1 2 3 template Next
                        Working...
                        X