Announcement

Collapse
No announcement yet.

issue with nxproxy

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • issue with nxproxy

    Hi
    I was wondering if someone could shed some light,
    Currently i have nxfilter installed on docker, and trying to install nxproxy on a windows machine, and i put the server IP which has the docker 192.168.7.89 and my windows machine another IP, i can ping it and access the webGUI so there is no issue on network
    but when i try test im getting this error see picture

    Thank you

    Click image for larger version

Name:	image.png
Views:	418
Size:	275.9 KB
ID:	2303

  • #2
    You need to change Login Token to yours. Login Token is a user property. You can see it when you go to an edit page of a user.

    Comment


    • #3
      Hi thanks for the reply, so i created the user with his login token but i keep getting the error
      i was checking the logs on the server side and i see this

      HTML Code:
      RHr, Login disabled for remote user! client IP = 192.168.21.45.
      Click image for larger version  Name:	image.png Views:	0 Size:	13.6 KB ID:	2316
      Click image for larger version  Name:	image.png Views:	0 Size:	34.0 KB ID:	2315
      Attached Files
      Last edited by killmasta93; 08-23-2023, 02:32 PM.

      Comment


      • #4
        Did you enable User Autentication on 'System > Setup'? If you already did it, look into /nxfilter/log/nxfilter.log when you do the test. You may need to enable debugging for NxFilter. https://tutorial.nxfilter.org/i-faq.php#enable-debug

        Comment


        • #5
          awsome that did the trick didnt know i had to check mark thank you again

          Comment


          • #6
            Hi @support200
            I was wondering if you can shed some light, so currently everything was working with the internal IP, now i need to expose the website, which im trying to do with a revese proxy


            but im having an issue, enabled the DEBUG mode on the server to see because on the client im putting the URL to point to nxfilter server

            Click image for larger version

Name:	image.png
Views:	218
Size:	11.2 KB
ID:	2327
            which im seeing these logs nxfilter

            HTML Code:
            | INFO [08-26 18:20:34] - MHMr, Stats, reqCnt = 1, blockCnt = 0, domainCnt = 1, userCnt = 1, tokenNameCnt = 1, cltIpCnt = 1, malwareCnt = 0, fwdErrCnt = 0, domainTestCnt = 0, xUserCnt = 0, xIpCnt = 0, xReqCnt = 0.
            nxfilter | INFO [08-26 18:20:34] - MHMr, Cache size = 10|0|0.
            nxfilter | DEBUG [08-26 18:20:48] - HxListener.doGet, cltIp = 192.168.7.147, domain = ping.signal.nxfilter.org, token = 4U1TEBFB, uname = Administrador, action = HX.
            nxfilter | DEBUG [08-26 18:20:48] - RpCQ, Parsing custom query, HX|ping.signal.nxfilter.org|4U1TEBFB|Administrador |192.168.7.147
            nxfilter | DEBUG [08-26 18:20:48] - RR, Custom query parsed.
            nxfilter | DEBUG [08-26 18:20:48] - RHr, RH #4, ping.signal.nxfilter.org, rqSize = 0, rDc = 1, rTtl = 0, rType = 1, cltIp = 192.168.7.147.
            nxfilter | DEBUG [08-26 18:20:48] - RequestHandler.findRemoteUser, Trying to find a remote user for ping.signal.nxfilter.org.
            nxfilter | DEBUG [08-26 18:20:48] - RequestHandler.findRemoteUser, Found a remote user by token, test.
            nxfilter | DEBUG [08-26 18:20:48] - LogFacade.addSignal1, 0|ping.signal.nxfilter.org|192.168.7.147|test_admi nistrador|||anon-grp|0|1||
            nxfilter | INFO [08-26 18:21:00] - LWf, logAll.logCnt = 1, logAll.signalCnt = 1, logAll.flowCnt = 0, logAll.recvFlow = 0.
            i also opened the ports

            Click image for larger version

Name:	image.png
Views:	194
Size:	20.1 KB
ID:	2328
            Click image for larger version

Name:	image.png
Views:	194
Size:	17.6 KB
ID:	2329

            Thank you

            Comment


            • #7
              What do you mean by URL? You are supposed to use an IP or domain there. Try IP and see if it's working and then domain. If your domain doesn't work thry to ping it on cmd.

              Comment


              • #8
                You also need to open TCP/443.

                Comment


                • #9
                  Thank you so much for the reply, whats odd is that it works the blocking,

                  currently this is what i have

                  192.168.7.147 192.168.7.89
                  nginx proxy---------nxfilter using port 8282

                  the NGINX proxy which has the SSL and is using 443 revese proxy into nxfilter 8282


                  i also tried IP same issue

                  very odd because on the logs it shows ping successful

                  Click image for larger version

Name:	image.png
Views:	221
Size:	118.7 KB
ID:	2333
                  Last edited by killmasta93; 08-27-2023, 07:01 PM.

                  Comment


                  • #10
                    I guess your DNS working and blocking working with NxProxy. Then what's not working and why do you need Reverse Proxy here?

                    If anything not working with NxProxy, it's about domain resolving. NxProxy doesn't block other traffic than UDP/53.

                    Comment


                    • #11
                      Oh gotcha, as i currently using reverse proxy to expose the port 443 but i guess if its working i guess i could leave it alone thank you again

                      Comment


                      • #12
                        hi so it seems i might found the issue just cant seem to solve it currently when i tries to ping it


                        Code:
                        "GET /hxlistener?action=HX&token=C7AP1HBX&domain=ping.signal.nxfilter.org HTTP/1.1" 301 162 "-" "-"
                        i tried on nginx to pass though
                        Code:
                        location /hxlistener {
                        rewrite ^/hxlistener(.*)$ $1 break;
                        set $upstream_port 8282;
                        set $upstream_proto http;
                        proxy_pass $upstream_proto://$upstream_app:$upstream_port;
                        proxy_set_header Host $host;
                        proxy_set_header X-Real-IP $remote_addr;
                        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                        }

                        Code:
                           location / {
                                proxy_set_header Host $host;
                                proxy_set_header X-Real-IP $remote_addr;
                                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                                set $upstream_app 192.168.7.89;
                                set $upstream_port 8282;
                                set $upstream_proto http;
                                proxy_pass $upstream_proto://$upstream_app:$upstream_port;
                        
                            }
                        but no luck so far

                        Comment


                        • #13
                          So, it's like when NxProxy outisde your local network and try to access NxFilter inside the network, the HTTPS traffic needs to go through your NGINX reverse proxy? Don't know if it works. Too much complicated. You could run NxFilter on cloud for NxProxy users. Might be easier.

                          Comment

                          Working...
                          X