{"id":189713,"date":"2025-06-10T12:11:14","date_gmt":"2025-06-10T10:11:14","guid":{"rendered":"https:\/\/fivemx.com\/?p=189713"},"modified":"2025-06-10T12:13:19","modified_gmt":"2025-06-10T10:13:19","slug":"solucao-de-problemas-fxserver-nao-esta-respondendo-como-consertar","status":"publish","type":"post","link":"https:\/\/fivemx.com\/pt\/troubleshooting-fxserver-is-not-responding-how-to-fix\/","title":{"rendered":"Solu\u00e7\u00e3o de problemas: FXServer n\u00e3o est\u00e1 respondendo! (Como corrigir)"},"content":{"rendered":"<p class=\"wp-block-paragraph\">Quando o seu FXServer apresenta erros de &quot;n\u00e3o est\u00e1 respondendo&quot;, voc\u00ea normalmente est\u00e1 lidando com um dos cinco problemas principais. Este guia fornece etapas sistem\u00e1ticas de solu\u00e7\u00e3o de problemas para administradores de servidores FiveM que enfrentam falhas de conectividade entre o txAdmin e o FXServer.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Causa principal: incompatibilidade de configura\u00e7\u00e3o de porta<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Emitir<\/strong>: txAdmin n\u00e3o consegue se conectar ao FXServer devido \u00e0 configura\u00e7\u00e3o incorreta da porta em server.cfg<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Consertar<\/strong>: Verifique se o seu server.cfg cont\u00e9m pontos de extremidade TCP\/UDP correspondentes:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">endpoint_add_tcp &quot;0.0.0.0:30120&quot; endpoint_add_udp &quot;0.0.0.0:30121&quot;\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Substitua os n\u00fameros das portas pelas portas alocadas. Se os n\u00fameros das portas n\u00e3o corresponderem \u00e0 sua porta de aloca\u00e7\u00e3o prim\u00e1ria, ocorrer\u00e3o erros de conex\u00e3o.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Etapas de valida\u00e7\u00e3o<\/strong>:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Verifique as configura\u00e7\u00f5es do txAdmin \u2192 FXServer para portas configuradas<\/li>\n\n\n\n<li>Compare com as declara\u00e7\u00f5es de endpoint server.cfg<\/li>\n\n\n\n<li>Reinicie o servidor via console ap\u00f3s as corre\u00e7\u00f5es<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Causa secund\u00e1ria: Conectividade do monitor txAdmin<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Emitir<\/strong>: txAdmin:Monitor n\u00e3o consegue se conectar ao FXServer, causando mensagens \u201cFXServer n\u00e3o est\u00e1 respondendo!\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Causas raiz<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>FXServer n\u00e3o est\u00e1 respondendo ao ponto de extremidade TCP (recurso travado)<\/li>\n\n\n\n<li>FXServer e txAdmin compartilhando a mesma porta TCP<\/li>\n\n\n\n<li>FXServer n\u00e3o escuta a interface local<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Consertar<\/strong>: Inicie o FXServer no modo monitor:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\"># Windows .\/FXServer.exe # Linux .\/run.sh\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Cr\u00edtico<\/strong>: N\u00e3o use argumentos +exec ao iniciar o txAdmin. O txAdmin requer que o FXServer seja executado no modo monitor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Interfer\u00eancia de antiv\u00edrus (Windows)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Emitir<\/strong>: A verifica\u00e7\u00e3o do diret\u00f3rio FXServer pelo antiv\u00edrus Microsoft Defender causa inicializa\u00e7\u00f5es lentas e tempos limite de conectividade<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Consertar<\/strong>: Adicionar diret\u00f3rio FXServer \u00e0 lista de exclus\u00e3o:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\"># Executar como administrador Add-MpPreference -ExclusionPath &quot;C:\\FXServer\\&quot;\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Substitua o caminho pelo local real do seu diret\u00f3rio FXServer.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Problemas de configura\u00e7\u00e3o de rede<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Emitir<\/strong>: NAT\/gateway mascarando portas de origem UDP ou encaminhamento de porta impr\u00f3prio<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Lista de verifica\u00e7\u00e3o de corre\u00e7\u00e3o<\/strong>:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Encaminhar portas TCP e UDP no roteador\/firewall<\/li>\n\n\n\n<li>Verifique se o Firewall do Windows permite FXServer.exe<\/li>\n\n\n\n<li>Verifique a configura\u00e7\u00e3o do NAT para preserva\u00e7\u00e3o da porta UDP<\/li>\n\n\n\n<li>Teste a conectividade local: <code>telnet localhost 30120<\/code><\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Bloqueio de recursos na inicializa\u00e7\u00e3o<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Emitir<\/strong>: Recursos travados impedem que o FXServer responda \u00e0s verifica\u00e7\u00f5es de integridade<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Abordagem diagn\u00f3stica<\/strong>:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Inicie o servidor com recursos m\u00ednimos<\/li>\n\n\n\n<li>Adicione recursos incrementalmente para identificar o culpado<\/li>\n\n\n\n<li>Verifique o console em busca de mensagens de erro de recursos<\/li>\n\n\n\n<li>Remover ou corrigir recursos problem\u00e1ticos<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Configura\u00e7\u00e3o de teste do server.cfg<\/strong>:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\"># Inicializa\u00e7\u00e3o m\u00ednima para teste garantir gerenciador de mapas garantir chat garantir gerenciador de spawn # Adicionar outros recursos um por um\n<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Solu\u00e7\u00e3o de problemas avan\u00e7ada<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Falhas na verifica\u00e7\u00e3o de integridade<\/strong>: O monitor mostra \u201cErro de solicita\u00e7\u00e3o HealthCheck: conex\u00e3o ECONNREFUSED\u201d, indicando perda completa de conectividade.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Etapas de verifica\u00e7\u00e3o<\/strong>:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Confirme o processo FXServer em execu\u00e7\u00e3o: <code>lista de tarefas | findstr FXServer<\/code><\/li>\n\n\n\n<li>Verifique a liga\u00e7\u00e3o da porta: <code>netstat -an | findstr :30120<\/code><\/li>\n\n\n\n<li><a href=\"https:\/\/fivemx.com\/pt\/como-verificar-se-ha-erros-nos-logs-do-txadmin\/\">Revisar logs do txAdmin <\/a>para padr\u00f5es de erro espec\u00edficos<\/li>\n\n\n\n<li>Teste com server.cfg novo usando <a href=\"https:\/\/docs.fivem.net\/docs\/server-manual\/setting-up-a-server-vanilla\/#servercfg\" target=\"_blank\" rel=\"noopener\">configura\u00e7\u00e3o padr\u00e3o do FiveM<\/a><\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Nota de incerteza<\/strong>:Alguns problemas de conectividade podem surgir de configura\u00e7\u00f5es de rede do provedor de hospedagem ou de pol\u00edticas regionais de firewall que n\u00e3o s\u00e3o imediatamente aparentes nos logs do servidor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Valida\u00e7\u00e3o de configura\u00e7\u00e3o<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Elementos server.cfg necess\u00e1rios<\/strong>:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\"># Essencial para conjuntos de listagem de servidores sv_projectName &quot;Nome do seu servidor&quot; define sv_projectDesc &quot;Descri\u00e7\u00e3o do seu servidor&quot; # Configura\u00e7\u00e3o correta do endpoint endpoint_add_tcp &quot;0.0.0.0:30120&quot; endpoint_add_udp &quot;0.0.0.0:30121&quot; # Habilitar integra\u00e7\u00e3o com o txAdmin iniciar o txAdmin\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Os servidores exibem erros se sv_projectName e sv_projectDesc n\u00e3o estiverem definidos.<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prioridade de resolu\u00e7\u00e3o<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Primeiro<\/strong>: Verifique a configura\u00e7\u00e3o da porta em server.cfg<\/li>\n\n\n\n<li><strong>Segundo<\/strong>: Inicie o FXServer sem argumentos +exec<\/li>\n\n\n\n<li><strong>Terceiro<\/strong>: Adicionar exclus\u00f5es de antiv\u00edrus<\/li>\n\n\n\n<li><strong>Quarto<\/strong>: Verifique as configura\u00e7\u00f5es de rede\/firewall<\/li>\n\n\n\n<li><strong>Quinto<\/strong>: Isolar recursos problem\u00e1ticos<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">A maioria dos erros \u201cFXServer n\u00e3o est\u00e1 respondendo\u201d s\u00e3o resolvidos por meio da corre\u00e7\u00e3o de incompatibilidades de porta entre os endpoints server.cfg e a configura\u00e7\u00e3o do txAdmin, seguido pela garantia de procedimentos adequados de inicializa\u00e7\u00e3o do modo monitor.<\/p>","protected":false},"excerpt":{"rendered":"<p>When your FXServer shows &#8220;not responding&#8221; errors, you&#8217;re typically dealing with one of five core issues. This guide provides systematic troubleshooting steps for FiveM server administrators experiencing connectivity failures between txAdmin and FXServer. Primary Cause: Port Configuration Mismatch Issue: txAdmin cannot connect to FXServer due to incorrect port configuration in server.cfg Fix: Verify your server.cfg [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":189160,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1900],"tags":[],"class_list":["post-189713","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-troubleshooting"],"blocksy_meta":[],"_links":{"self":[{"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/posts\/189713","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/comments?post=189713"}],"version-history":[{"count":0,"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/posts\/189713\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/media\/189160"}],"wp:attachment":[{"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/media?parent=189713"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/categories?post=189713"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/tags?post=189713"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}