Cloudflare http 530 error in loadbalance 3 machines+ cloud for saas + cross domain

What is the name of the domain?

znap.dev.br

What is the error number?

530

What is the error message?

no error only status code 530

What is the issue you’re encountering

error status 530 http

What feature, service or problem is this related to?

I don’t know

What are the steps to reproduce the issue?

Until yesterday was working fine and today begin this problem

Título: Erro HTTP 530 em ambiente com Cloudflare for SaaS e Load Balancer – Ajuda por favor!

Contexto do Ambiente:

  • DNS e Domínios:
    • Nosso cliente possui o DNS na KingHost e criamos os subdomínios:
      • app.dominio_do_cliente
      • api-app.dominio_do_cliente
    • Nosso aplicativo utiliza os domínios:
      • app.meudominio
      • api-app.meudominio
    • Os domínios do aplicativo estão gerenciados pelo Cloudflare.
  • Infraestrutura:
    • Na Cloudflare, configuramos dois Load Balancers (um para cada domínio do app e api) que direcionam as requisições para 3 máquinas com Nginx na minha cloud provider.
    • Configuramos o Cloudflare for SaaS para possibilitar o cross-domain, permitindo que as requisições do dns do cliente sejam respondidas no meu dns, conforme a documentação oficial developers.cloudflare/cloudflare-for-platforms/cloudflare-for-saas/.
    • Os certificados digitais foram criados e estão sendo gerenciados pelo Cloudflare.

Problema:

  • Até ontem, tudo funcionava normalmente.
  • Hoje, de repente, estamos recebendo erro HTTP 530.
  • Todas as configurações e infraestrutura permanecem idênticas às de ontem.

Passos de Verificação Realizados:

  1. DNS e CNAME:
  • Verifiquei que os registros DNS nos respectivos provedores (KingHost e Cloudflare) continuam apontando corretamente para os Load Balancers.
  1. Load Balancer e Health Checks:
  • Os health checks configurados no Load Balancer não indicam problemas nos servidores Nginx (Contabo).
  1. Logs do Servidor (Nginx):
  • Analisei os logs e não encontrei erros ou indícios de que as requisições estejam sendo bloqueadas ou rejeitadas.
  1. Configuração SSL/TLS:
  • A configuração de SSL/TLS continua inalterada e os certificados digitais estão válidos e corretamente provisionados.
  1. Cloudflare for SaaS:
  • A configuração para o custom hostname e cross-domain permanece conforme as recomendações da documentação oficial.

Perguntas / Solicitação:

  • Alguém já passou por um problema semelhante com erro HTTP 530 nesse tipo de ambiente?
  • Quais pontos adicionais posso verificar ou configurar para identificar a origem do problema?
  • Alguma sugestão ou dica de troubleshooting que possa ajudar a resolver essa situação?

Qualquer contribuição é bem-vinda. Estou utilizando o plano gratuito da Cloudflare, então não tenho acesso ao suporte direto.

Title: HTTP 530 Error in Cloudflare for SaaS Environment with Load Balancer – Need Assistance!

Environment Context:

  • DNS and Domains:
    • Our client’s DNS is hosted on KingHost, where we created the following subdomains:
      • app.domain_customer
      • api-app.domain_customer
    • Our application uses the domains:
      • app.my_saas_domain
      • api-app.my_saas_domain
    • The application’s domains are managed by Cloudflare.
  • Infrastructure:
    • In Cloudflare, we configured two Load Balancers (one for each application domain) that direct requests to three Nginx servers hosted on Contabo.
    • We set up Cloudflare for SaaS to enable cross-domain functionality, allowing requests from customer domain to be served on my saas domain, following the official documentation developers.cloudflare/cloudflare-for-platforms/cloudflare-for-saas/.
    • Digital certificates were created and are being managed by Cloudflare.

Problem:

  • Everything was working normally until yesterday.
  • Today, suddenly, we are receiving an HTTP 530 error.
  • All configurations and infrastructure remain unchanged from yesterday.

Verification Steps Taken:

  1. DNS and CNAME Records:
  • Verified that the DNS records at KingHost and Cloudflare are still correctly pointing to the Load Balancers.
  1. Load Balancer and Health Checks:
  • The health checks configured on the Load Balancer do not show any issues with the Nginx servers on Contabo.
  1. Server Logs (Nginx):
  • Reviewed the Nginx logs and did not find any errors or indications that requests are being blocked or rejected.
  1. SSL/TLS Configuration:
  • The SSL/TLS settings remain unchanged, and the digital certificates are valid and properly provisioned.
  1. Cloudflare for SaaS:
  • The configuration for custom hostnames and cross-domain is still in line with the recommendations in the official documentation.

Questions / Request for Help:

  • Has anyone experienced a similar issue with an HTTP 530 error in this type of environment?
  • What additional areas should I check or configure to help identify the root cause of the problem?
  • Any suggestions or troubleshooting tips to resolve this issue?

Any input is greatly appreciated, as I’m on the free plan and do not have direct support access.

Note: When accessing the application directly (bypassing Cloudflare), it works perfectly. The issue appears to be isolated to Cloudflare.

The same problem.

There is no way to solve it; it is an intermittent error.

I have currently switched back to the original server and am no longer using Cloudflare.

I don’t know if the configuration is exactly the same, but I also started getting the 530 error.

530 did not occur before, and I did not change the server configuration, but it started occurring from February 21st.

When I changed my plan to business to make an inquiry, it somehow stopped happening. .

I am also getting random 530 errors on my domain since last night, also accessed through saas. May I ask how you solved it.

I have the same problem. Since yesterday, the js and css on my website have started to have intermittent and random 530 errors. Is there any way to solve it?

Hey,

Can you all please share a repro url?
@liquidsportal @cjjdaq @izumi @wood @cloud27

Thanks for the reports, the issue is now resolved - sorry for the inconvience!

2 Likes

Thank you for everything you have done

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.