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

    WHATSAPP NAO CARREGA QR CODE (WHATSAPP WEB)

    Scheduled Pinned Locked Moved Portuguese
    9 Posts 8 Posters 20.8k 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.
    • M
      MayqueSouza
      last edited by

      Bom dia Amigos,

      Navegando pelo PfSense o QR Code do web.whatsapp.com não carrega, fica apenas "girando".

      Já liberei todas as portas do CIDR's em rules (coletados no próprio site do whats) tanto na porta WAN quanto na LAN.
      Atualmente estou analisando em STATUS>System Logs>Firewall Alguns bloqueios das portas e liberando lá pelo "Easy Rule" Onde ele adiciona automaticamente a liberação dos ips bloqueados, porém, ainda assim não carrega o bendito do QR Code.

      Alguma sugestão?
      Obrigado.

      1 Reply Last reply Reply Quote 0
      • G
        Gydeon
        last edited by

        Cara faz da maneira mais fácil e simples, pega todas essas redes da CIDR do Whatsapp e add no "Bypass", Pronto vc não irá ter mais problemas com o whatsapp.

        31.13.64.51/32;
        31.13.65.49/32;
        31.13.66.49/32;
        31.13.67.51/32;
        31.13.68.52/32;
        31.13.69.240/32;
        31.13.70.49/32;
        31.13.71.49/32;
        31.13.72.52/32;
        31.13.73.49/32;
        31.13.74.49/32;
        31.13.75.52/32;
        31.13.76.81/32;
        31.13.77.49/32;
        31.13.78.53/32;
        31.13.79.195/32;
        31.13.80.53/32;
        31.13.81.53/32;
        31.13.82.51/32;
        31.13.83.51/32;
        31.13.84.51/32;
        31.13.85.51/32;
        31.13.86.51/32;
        31.13.87.51/32;
        31.13.88.49/32;
        31.13.90.51/32;
        31.13.91.51/32;
        31.13.92.52/32;
        31.13.93.51/32;
        31.13.95.63/32;
        50.22.198.204/30;
        50.22.210.32/30;
        50.22.210.128/27;
        50.22.225.64/27;
        50.22.235.248/30;
        50.22.240.160/27;
        50.23.90.128/27;
        50.97.57.128/27;
        75.126.39.32/27;
        108.168.174.0/27;
        108.168.176.192/26;
        108.168.177.0/27;
        108.168.180.96/27;
        108.168.254.65/32;
        108.168.255.224/32;
        108.168.255.227/32;
        158.85.0.96/27;
        158.85.5.192/27;
        158.85.46.128/27;
        158.85.48.224/27;
        158.85.58.0/25;
        158.85.61.192/27;
        158.85.224.160/27;
        158.85.233.32/27;
        158.85.249.128/27;
        158.85.249.224/27;
        158.85.254.64/27;
        169.44.36.0/25;
        169.44.58.64/27;
        169.44.80.0/26;
        169.45.71.32/27;
        169.45.71.96/27;
        169.45.87.128/26;
        169.45.169.192/27;
        169.45.182.96/27;
        169.45.214.224/27;
        169.45.219.224/27;
        169.45.237.192/27;
        169.45.238.32/27;
        169.53.29.128/27;
        169.53.71.224/27;
        169.53.250.128/26;
        169.54.2.160/27;
        169.54.44.224/27;
        169.54.51.32/27;
        169.54.55.192/27;
        169.54.210.0/27;
        169.54.222.128/27;
        169.55.69.128/26;
        169.55.74.32/27;
        169.55.126.64/26;
        169.55.210.96/27;
        169.55.235.160/27;
        173.192.162.32/27;
        173.192.219.128/27;
        173.192.222.160/27;
        173.192.231.32/27;
        173.193.205.0/27;
        173.193.230.96/27;
        173.193.230.128/27;
        173.193.230.192/27;
        173.193.239.0/27;
        174.36.208.128/27;
        174.36.210.32/27;
        174.36.251.192/27;
        174.37.199.192/27;
        174.37.217.64/27;
        174.37.231.64/27;
        174.37.243.64/27;
        174.37.251.0/27;
        179.60.192.51/32;
        179.60.193.51/32;
        179.60.195.51/32;
        184.173.136.64/27;
        184.173.147.32/27;
        184.173.161.64/32;
        184.173.161.160/27;
        184.173.173.116/32;
        184.173.179.32/27;
        185.60.216.53/32;
        192.155.212.192/27;
        198.11.193.182/31;
        198.11.251.32/27;
        198.23.80.0/27;
        208.43.115.192/27;
        208.43.117.79/32;
        208.43.122.128/27;
        
        
        1 Reply Last reply Reply Quote 0
        • M
          MayqueSouza
          last edited by

          Boa noite amigo, efetuei os procedimento e está funcional, porém, esta regra libera para toda minha rede. Teria alguma possibilidade de liberá-lo apenas para um grupo de pessoas? (configurável)
            Como seria?
            Obrigado.

          1 Reply Last reply Reply Quote 0
          • T
            tomaswaldow
            last edited by

            Sim, cria um Alias com os IPs e coloca em Source na regra do Whastapp;

            Tomas @ 2W Consultoria

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

              Pessoal!
              Encontrei uma solução muito simples para esse incidente, basta adicionar os endereços abaixo no Bypass Destination. Fazendo isso o QR Code irá carregar normalmente.

              Bypass Proxy for These Destination IPs:

              ;web.whatsapp.com
              ;w1.web.whatsapp.com
              ;w2.web.whatsapp.com
              ;w3.web.whatsapp.com
              ;w4.web.whatsapp.com
              ;w5.web.whatsapp.com
              ;w6.web.whatsapp.com
              ;w7.web.whatsapp.com
              ;w8.web.whatsapp.com

              Att,
              Rafael Giffone - Support Analyst

              1 Reply Last reply Reply Quote 0
              • F
                Flávio Candeias
                last edited by

                PESSOAL, ACABEI DE RESOLVER O PROBLEMA.... SIMPLESMENTE A VERSÃO DO FIREFOX 65 NÃO CARREGA A BENDITA IMAGEM, TROQUEI PARA A VERSÃO 62.0 DO FIREFOX E FUNCIONOU DE BOA

                1 Reply Last reply Reply Quote 0
                • E
                  edu.fa
                  last edited by

                  pessoal, ninguem mais sobre com esse problema ?

                  vira e mexe eu tenho esse problema, descubro IP do zap\face, libero e tempos depois bloqueia

                  1 Reply Last reply Reply Quote 0
                  • lotusL
                    lotus
                    last edited by

                    veja se as portas 80 e 443 estão liberadas corretamente (é por essas portas que o whats trabalha na web) as outras portas sera preciso para texto, voz, video e imagem...etc, quanto aos sites, so tem 2 que ele precisa usar, whatsapp.com e whatsapp.net.
                    Dessa forma que no meu cenário e funciona normalmente inclusive atravez do e2guardian, lista CDIR nunca funcionou pra mim.

                    G 1 Reply Last reply Reply Quote 0
                    • G
                      ghislenidroid @lotus
                      last edited by

                      @lotus No E2Guardians eu inseri na guia ACL, Exception os endereços abaixo;
                      whatsapp.com
                      31.13.67.52
                      2a03:2880:f22c:c5:face:b00c::167
                      mmx-ds.cdn.whatsapp.net

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