Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    [SOLUCIONADO] Despues de Actualizar a 2.1.1 no puedo acceder a pfSense via web

    Scheduled Pinned Locked Moved Español
    19 Posts 4 Posters 6.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • pttP
      ptt Rebel Alliance
      last edited by

      https://doc.pfsense.org/index.php/I_locked_myself_out_of_the_WebGUI,_help!

      1 Reply Last reply Reply Quote 0
      • R
        Ricardozam
        last edited by

        @ptt:

        https://doc.pfsense.org/index.php/I_locked_myself_out_of_the_WebGUI,_help!

        De esos metodos solo me funciono con putty

        Remotely Circumvent Firewall Lockout With SSH Tunneling

        la regla Anti-Lockout esta activa y veo que tengo todos los servicios asi:

        Service	        Description	                                                     Status	 
apinger	        Gateway Monitoring Daemon	                             funcionando
bsnmpd	        SNMP Service	                                                     funcionando
c-icap	        Icap inteface for squid and clamav integration     funcionando
clamd	        Clamav Antivirus	                                             funcionando
darkstat           Darkstat bandwidth monitoring daemon              caído
dhcpd	        DHCP Service	                                                     funcionando
dnsmasq	        DNS Forwarder 	                                             funcionando
ntpd	                NTP clock sync	                                                     funcionando
squid	        Proxy server Service	                                     caído
squidGuard	Proxy server filter Service                                     caído

        System log

        Apr 5 21:07:30	squid: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory
Apr 5 21:07:28	php: /status_services.php: The command '/usr/local/etc/rc.d/squid.sh stop' returned exit code '1', the output was '2014/04/05 21:07:23| ERROR: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory squid: No running copy'
Apr 5 21:00:13	sshd[99074]: Accepted keyboard-interactive/pam for admin from 172.16.1.201 port 2245 ssh2
Apr 5 21:00:00	php: sarg.php: The command 'export LC_ALL=C && /usr/pbi/sarg-i386/bin/sarg ' returned exit code '1', the output was 'SARG: File not found: /var/log/squid/access.log'
Apr 5 21:00:00	php: sarg.php: Sarg: force refresh now with args, compress() and none action after sarg finish.
Apr 5 20:00:01	php: sarg.php: The command 'export LC_ALL=C && /usr/pbi/sarg-i386/bin/sarg ' returned exit code '1', the output was 'SARG: File not found: /var/log/squid/access.log'
Apr 5 20:00:00	php: sarg.php: Sarg: force refresh now with args, compress() and none action after sarg finish.
Apr 5 19:28:10	squid: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory
Apr 5 19:28:08	php: /status_services.php: The command '/usr/local/etc/rc.d/squid.sh stop' returned exit code '1', the output was '2014/04/05 19:28:03| ERROR: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory squid: No running copy'
Apr 5 19:27:57	ipfw-classifyd: Loaded Protocol: tesla (rule action block)
Apr 5 19:27:57	ipfw-classifyd: Loaded Protocol: napster (rule action block)
Apr 5 19:27:57	ipfw-classifyd: Loaded Protocol: jabber (rule action block)
Apr 5 19:27:57	ipfw-classifyd: Loaded Protocol: gnutella (rule action block)
Apr 5 19:27:57	ipfw-classifyd: Loaded Protocol: edonkey (rule action block)
Apr 5 19:27:57	ipfw-classifyd: Loaded Protocol: bittorrent (rule action block)
Apr 5 19:27:57	ipfw-classifyd: Loaded Protocol: ares (rule action block)
Apr 5 19:27:57	ipfw-classifyd: Reloading config...
Apr 5 19:27:32	php: rc.filter_configure_sync: Sending HUP signal to 17984
Apr 5 19:27:32	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "filter" rules.
Apr 5 19:27:32	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "pfearly" rules.
Apr 5 19:27:32	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "nat" rules.
Apr 5 19:27:30	check_reload_status: Reloading filter
Apr 5 19:27:28	php: /pkg_mgr_install.php: Beginning package installation for darkstat .
Apr 5 19:27:27	check_reload_status: Syncing firewall
Apr 5 19:27:26	check_reload_status: Syncing firewall
Apr 5 19:26:36	squid: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory
Apr 5 19:26:34	php: /status_services.php: The command '/usr/local/etc/rc.d/squid.sh stop' returned exit code '1', the output was '2014/04/05 19:26:29| ERROR: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory squid: No running copy'
Apr 5 19:25:58	ipfw-classifyd: Loaded Protocol: tesla (rule action block)
Apr 5 19:25:58	ipfw-classifyd: Loaded Protocol: napster (rule action block)
Apr 5 19:25:58	ipfw-classifyd: Loaded Protocol: jabber (rule action block)
Apr 5 19:25:58	ipfw-classifyd: Loaded Protocol: gnutella (rule action block)
Apr 5 19:25:58	ipfw-classifyd: Loaded Protocol: edonkey (rule action block)
Apr 5 19:25:58	ipfw-classifyd: Loaded Protocol: bittorrent (rule action block)
Apr 5 19:25:58	ipfw-classifyd: Loaded Protocol: ares (rule action block)
Apr 5 19:25:58	ipfw-classifyd: Reloading config...
Apr 5 19:25:46	php: rc.filter_configure_sync: Sending HUP signal to 17984
Apr 5 19:25:46	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "filter" rules.
Apr 5 19:25:45	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "pfearly" rules.
Apr 5 19:25:45	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "nat" rules.
Apr 5 19:25:45	php: rc.filter_configure_sync: Sending HUP signal to 17984
Apr 5 19:25:45	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "filter" rules.
Apr 5 19:25:44	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "pfearly" rules.
Apr 5 19:25:44	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "nat" rules.
Apr 5 19:25:42	check_reload_status: Reloading filter
Apr 5 19:25:42	check_reload_status: Syncing firewall
Apr 5 19:25:42	check_reload_status: Reloading filter
Apr 5 19:25:38	php: rc.filter_configure_sync: Sending HUP signal to 17984
Apr 5 19:25:38	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "filter" rules.
Apr 5 19:25:33	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "pfearly" rules.
Apr 5 19:25:32	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "nat" rules.
Apr 5 19:25:31	php: /pkg_mgr_install.php: The command '/usr/pbi/squid-i386/sbin/squid -f /usr/pbi/squid-i386/etc/squid/squid.conf' returned exit code '1', the output was '2014/04/05 19:25:31| ERROR: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory FATAL: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory Squid Cache (Version 3.3.10): Terminated abnormally. CPU Usage: 0.010 seconds = 0.010 user + 0.000 sys Maximum Resident Size: 35776 KB Page faults with physical i/o: 0'
Apr 5 19:25:31	squid: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory
Apr 5 19:25:31	php: /pkg_mgr_install.php: Starting Squid
Apr 5 19:25:30	php: /pkg_mgr_install.php: [Squid] - Squid_resync function call pr: bp: rpc:no
Apr 5 19:25:28	check_reload_status: Reloading filter
Apr 5 19:25:28	ipfw-classifyd: Loaded Protocol: tesla (rule action block)
Apr 5 19:25:28	ipfw-classifyd: Loaded Protocol: napster (rule action block)
Apr 5 19:25:28	ipfw-classifyd: Loaded Protocol: jabber (rule action block)
Apr 5 19:25:28	ipfw-classifyd: Loaded Protocol: gnutella (rule action block)
Apr 5 19:25:28	ipfw-classifyd: Loaded Protocol: edonkey (rule action block)
Apr 5 19:25:28	ipfw-classifyd: Loaded Protocol: bittorrent (rule action block)
Apr 5 19:25:28	ipfw-classifyd: Loaded Protocol: ares (rule action block)
Apr 5 19:25:28	ipfw-classifyd: Reloading config...
Apr 5 19:25:28	php: rc.filter_configure_sync: Sending HUP signal to 17984
Apr 5 19:25:28	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "filter" rules.
Apr 5 19:25:25	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "pfearly" rules.
Apr 5 19:25:24	php: rc.filter_configure_sync: SQUID is installed but not started. Not installing "nat" rules.
Apr 5 19:25:18	php: /pkg_mgr_install.php: The command '/usr/pbi/squid-i386/sbin/squid -f /usr/pbi/squid-i386/etc/squid/squid.conf' returned exit code '1', the output was '2014/04/05 19:25:18| ERROR: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory FATAL: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory Squid Cache (Version 3.3.10): Terminated abnormally. CPU Usage: 0.010 seconds = 0.010 user + 0.000 sys Maximum Resident Size: 27392 KB Page faults with physical i/o: 0'
Apr 5 19:25:18	squid: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory
Apr 5 19:25:18	php: /pkg_mgr_install.php: Starting Squid
Apr 5 19:25:18	check_reload_status: Syncing firewall
Apr 5 19:25:17	php: /pkg_mgr_install.php: [Squid] - Squid_resync function call pr: bp: rpc:no
Apr 5 19:25:17	check_reload_status: Reloading filter
Apr 5 19:25:17	squid: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory
Apr 5 19:25:17	php: /pkg_mgr_install.php: Starting a proxy monitor script
Apr 5 19:25:17	php: /pkg_mgr_install.php: Starting Squid
Apr 5 19:25:16	php: /pkg_mgr_install.php: Stopping any running proxy monitors
Apr 5 19:25:15	check_reload_status: Syncing firewall
Apr 5 19:24:58	ipfw-classifyd: Loaded Protocol: tesla (rule action block)
Apr 5 19:24:58	ipfw-classifyd: Loaded Protocol: napster (rule action block)
Apr 5 19:24:58	ipfw-classifyd: Loaded Protocol: jabber (rule action block)
Apr 5 19:24:58	ipfw-classifyd: Loaded Protocol: gnutella (rule action block)
Apr 5 19:24:58	ipfw-classifyd: Loaded Protocol: edonkey (rule action block)
Apr 5 19:24:58	ipfw-classifyd: Loaded Protocol: bittorrent (rule action block)
Apr 5 19:24:58	ipfw-classifyd: Loaded Protocol: ares (rule action block)
Apr 5 19:24:58	ipfw-classifyd: Reloading config...
Apr 5 19:24:56	php: rc.filter_configure_sync: Sending HUP signal to 17984
Apr 5 19:24:54	php: /pkg_mgr_install.php: Beginning package installation for squid3-dev .
Apr 5 19:24:53	check_reload_status: Reloading filter
Apr 5 19:24:52	check_reload_status: Syncing firewall
Apr 5 19:24:50	php: /pkg_mgr_install.php: The command '/usr/local/etc/rc.d/squid.sh stop' returned exit code '1', the output was '2014/04/05 19:24:45| ERROR: redirect_program /usr/pbi/squidguard-i386/bin/squidGuard: (2) No such file or directory squid: No running copy'
Apr 5 19:24:45	check_reload_status: Syncing firewall
Apr 5 19:22:30	ipfw-classifyd: Loaded Protocol: tesla (rule action block)
Apr 5 19:22:30	ipfw-classifyd: Loaded Protocol: napster (rule action block)
Apr 5 19:22:30	ipfw-classifyd: Loaded Protocol: jabber (rule action block)
Apr 5 19:22:30	ipfw-classifyd: Loaded Protocol: gnutella (rule action block)
Apr 5 19:22:30	ipfw-classifyd: Loaded Protocol: edonkey (rule action block)
Apr 5 19:22:30	ipfw-classifyd: Loaded Protocol: bittorrent (rule action block)
Apr 5 19:22:30	ipfw-classifyd: Loaded Protocol: ares (rule action block)
Apr 5 19:22:30	ipfw-classifyd: Reloading config..
```.
        1 Reply Last reply Reply Quote 0
        • R
          Ricardozam
          last edited by

          Ok problema resuelto

          Por alguna extraña razón la actualización a 2.1.1 modifico la parte de integraciones con Squidguard y eso evitaba que funcionara

          después de la actualización estaban asi:

          url_rewrite_program /usr/pbi/squidguard-i386/bin/squidGuard -c /usr/pbi/squidguard-i386/etc/squidGuard/squidGuard.conf;url_rewrite_bypass off;redirect_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;redirector_bypass off;url_rewrite_children 5

          pero me funcionaron asi:

          url_rewrite_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;url_rewrite_bypass off;redirect_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;redirector_bypass off;url_rewrite_children 5

          y pude acceder al box a través de http como antes

          A darkstat v3.0.714 platform: 1.2.1 no logre hacerlo funcionar a pesar de deinstalarlo e instalarlo dos veces y de haber arrancado el servicio, en su pantalla dice

          Se encontró el siguiente error al intentar recuperar la dirección URL: http://172.16.1.3:666/

Acceso Denegado

La configuración de control de acceso evita que su solicitud sea permitida en este momento. Por favor, póngase en contacto con su proveedor de servicios si cree que esto es incorrecto.

Su administrador del caché es admin@server

          no se si es por incompatibilidad con 2.1.1

          gracias por la orientación

          Ricardo

          1 Reply Last reply Reply Quote 0
          • L
            LEPM
            last edited by

            Puedes seguir teniendo problemas…
            las 2 config,de integrations(la que no funcion y la que si...), estan duplicadas, usando primero usando "url_rewrite_program" y luego "redirect_program"

            http://www.squid-cache.org/Doc/config/url_rewrite_program/

            Your new system is probably coming with some hyper trash like Windows 8

            1 Reply Last reply Reply Quote 0
            • belleraB
              bellera
              last edited by

              Se encontró el siguiente error al intentar recuperar la dirección URL: http://172.16.1.3:666/

              Acceso Denegado

              Lo más probable es que te falte permitir el puerto 666 en squid. El aviso es del squid.

              Proxy server: Access control: Squid Allowed ports

              squid3 –--> https://forum.pfsense.org/index.php?topic=73007.msg402349#msg402349
              squidGuard-squid3 ----> https://forum.pfsense.org/index.php?topic=73740.0

              1 Reply Last reply Reply Quote 0
              • R
                Ricardozam
                last edited by

                @LEPM:

                Puedes seguir teniendo problemas…
                las 2 config,de integrations(la que no funcion y la que si...), estan duplicadas, usando primero usando "url_rewrite_program" y luego "redirect_program"

                http://www.squid-cache.org/Doc/config/url_rewrite_program/

                ¿Lo correcto es solo esto?:

                url_rewrite_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;url_rewrite_bypass off;url_rewrite_children 16

                es lo que tenia antes como integración en 2.1 pero después del update a la versión 2.1.1

                me quedaba así, pero squid no arrancaba

                url_rewrite_program /usr/pbi/squidguard-i386/bin/squidGuard -c /usr/pbi/squidguard-i386/etc/squidGuard/squidGuard.conf;url_rewrite_bypass off;redirect_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;redirector_bypass off;url_rewrite_children 5

                así que lo cambie a esto, y así si si arrancó

                url_rewrite_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;url_rewrite_bypass off;redirect_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;redirector_bypass off;url_rewrite_children 5

                Pero no se por qué ocurrió ese cambio durante el update a la versión 2.1.1
                Mi duda ahora es en esta instrucción que antes era:

                url_rewrite_children 16
```pero el update la dejó en```
url_rewrite_children 5

                y como puede afectar el rendimiento

                Gracias por tu ayuda

                Ricardo

                1 Reply Last reply Reply Quote 0
                • R
                  Ricardozam
                  last edited by

                  @bellera:

                  Se encontró el siguiente error al intentar recuperar la dirección URL: http://172.16.1.3:666/

                  Acceso Denegado

                  Lo más probable es que te falte permitir el puerto 666 en squid. El aviso es del squid.

                  Proxy server: Access control: Squid Allowed ports

                  squid3 –--> https://forum.pfsense.org/index.php?topic=73007.msg402349#msg402349
                  squidGuard-squid3 ----> https://forum.pfsense.org/index.php?topic=73740.0

                  Efectivamente era eso en
                  Proxy Server -> ACLs -> Squid Allowed ports
                  en acl safeports

                  otro cambio del update porque antes me funcionaba en 2.1, en fin

                  Gracias por su ayuda

                  Ricardo

                  1 Reply Last reply Reply Quote 0
                  • L
                    LEPM
                    last edited by

                    @Ricardozam:

                    así que lo cambie a esto, y así si si arrancó

                    url_rewrite_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;url_rewrite_bypass off;redirect_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;redirector_bypass off;url_rewrite_children 5

                    url_rewrite_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf

                    lo siguiente es lo mismo,pero usando redirect_program que es sintaxis vieja

                    redirect_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf

                    mira este hilo en Documentacion:

                    https://forum.pfsense.org/index.php?topic=73740.0

                    Your new system is probably coming with some hyper trash like Windows 8

                    1 Reply Last reply Reply Quote 0
                    • R
                      Ricardozam
                      last edited by

                      mira este hilo en Documentacion:

                      https://forum.pfsense.org/index.php?topic=73740.0

                      Ok gracias ya lo entendí, la sintaxis vieja debe haberse puesto cuando se realizó el update a la version 2.1.1

                      Gracias por tu ayuda

                      Ricardo

                      1 Reply Last reply Reply Quote 0
                      • R
                        Ricardozam
                        last edited by

                        Por cierto hice los cambios pero esta ocurriendo algo extraño

                        cuando cambio en customs settings -> integrations a esto

                        url_rewrite_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;
url_rewrite_bypass off;
url_rewrite_children 16 startup=8 idle=4 concurrency=0

                        y reinicio el proxy solamente los cambios se conservan

                        pero si reinicio la box PfSense mediante Diagnostics -> Reboot

                        al volver a revisar tengo de nuevo esto en integrations

                        url_rewrite_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;
url_rewrite_bypass off;
redirect_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;redirector_bypass off;
url_rewrite_children 5

                        ¿Qué puede estar pasando que me vuelve a la configuración vieja?

                        Gracias por su ayuda

                        Ricardo

                        1 Reply Last reply Reply Quote 0
                        • L
                          LEPM
                          last edited by

                          realiza los cambios con squidGuard detenido.

                          Your new system is probably coming with some hyper trash like Windows 8

                          1 Reply Last reply Reply Quote 0
                          • R
                            Ricardozam
                            last edited by

                            @LEPM:

                            realiza los cambios con squidGuard detenido.

                            Cuando detengo el servicio de squid pierdo el acceso al box pfsense via web!!!!!!

                            ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ???

                            y tengo entonces que acceder mediante tunneling SSL via puTTy para iniciarlo de nuevo y reganar acceso a pfSense via web

                            Esto no ocurría antes es muy extraño

                            :o :o :o :o :o :o :o :o :o :o :o :o :o :o :o :o :o :o :o :o :o

                            ¿alguna idea?

                            Gracias por su ayuda

                            Ricardo

                            1 Reply Last reply Reply Quote 0
                            • L
                              LEPM
                              last edited by

                              @Ricardozam:

                              Cuando detengo el servicio de squid pierdo el acceso al box pfsense via web!!!!!!

                              Debes tener una regla que te permita solo llegar a lanaddress por http,https,ssh(ideal un alias,con esos puertos).

                              los cambios en: /usr/local/pkg/squidguard_configurator.inc
                              indicados en: https://forum.pfsense.org/index.php?topic=73740.0
                              los realizaste?

                              si estan echos prueba:

                              deshabilita squidguard desde el gui(desmarca enable),guarda los cambios.
                              luego en squid/integrations,agrega:

                              url_rewrite_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;
url_rewrite_bypass off;
url_rewrite_children 16 startup=8 idle=4 concurrency=0

                              salva los cambios,luego por si acaso,por ssh squid -k reconfigure,si no hay errores
                              revisa nuevamente integrations,si no ha cambiado nada.
                              ahora habilita squidguard,save,apply.
                              revisa nuevamente integrations.

                              Your new system is probably coming with some hyper trash like Windows 8

                              1 Reply Last reply Reply Quote 0
                              • R
                                Ricardozam
                                last edited by

                                Debes tener una regla que te permita solo llegar a lanaddress por http,https,ssh(ideal un alias,con esos puertos).

                                los cambios en: /usr/local/pkg/squidguard_configurator.inc
                                indicados en: https://forum.pfsense.org/index.php?topic=73740.0
                                los realizaste?

                                si estan echos prueba:

                                Si fueron hechos en la version 2.1 antes del update a la version 2.1.1 y todo funcionaba perfecro

                                deshabilita squidguard desde el gui(desmarca enable),guarda los cambios.
                                luego en squid/integrations,agrega:
                                Code: [Select]
                                url_rewrite_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;
                                url_rewrite_bypass off;
                                url_rewrite_children 16 startup=8 idle=4 concurrency=0

                                salva los cambios,luego por si acaso,por ssh squid -k reconfigure,si no hay errores
                                revisa nuevamente integrations,si no ha cambiado nada.
                                ahora habilita squidguard,save,apply.
                                revisa nuevamente integrations.

                                Segui el procedimiento exactamente pero cuando al final reviso integrations, tengo ahora:

                                url_rewrite_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;
                                url_rewrite_bypass off;
                                redirect_program /usr/pbi/squidguard-squid3-i386/bin/squidGuard -c /usr/pbi/squidguard-squid3-i386/etc/squidGuard/squidGuard.conf;redirector_bypass off;
                                url_rewrite_children 5

                                muy extraño

                                :o :o :o :o :o :o :o :o :o :o

                                1 Reply Last reply Reply Quote 0
                                • belleraB
                                  bellera
                                  last edited by

                                  @Ricardozam:

                                  ¿Qué puede estar pasando que me vuelve a la configuración vieja?

                                  Es un bug del paquete squidGuard para squid3, https://forum.pfsense.org/index.php?topic=73740.0

                                  @LEPM:

                                  luego en squid/integrations,agrega:

                                  Volverá a ser machacado al hacer [Apply] en squidGuard o reiniciar el equipo.

                                  Hay que pachear el código tal como hace días indiqué, https://forum.pfsense.org/index.php?topic=73740.0

                                  @Ricardozam:

                                  Cuando detengo el servicio de squid pierdo el acceso al box pfsense via web!!!!!!

                                  Postea con squid en marcha y detenido la salida de:

                                  pfctl -s rules | grep 312
pfctl -s nat | grep 312
ps aux | grep ^proxy
                                  1 Reply Last reply Reply Quote 0
                                  • R
                                    Ricardozam
                                    last edited by

                                    Problema solucionado con esto https://forum.pfsense.org/index.php?topic=73740.0

                                    Yo había hecho esos cambio en la versión 2.1 pero cuando actualicé a la 2.1.1 parece que se deshizo todo de nuevo

                                    También parece que se corrigió la pérdida del acceso al box vía web con este cambio
                                    reinicie y desactive varias veces squid y no ocurrió ese problema nuevamente

                                    Gracias de nuevo por su ayuda

                                    Ricardo

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post
                                    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.