{"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":"depannage-fxserver-ne-repond-pas-comment-resoudre-le-probleme","status":"publish","type":"post","link":"https:\/\/fivemx.com\/fr\/troubleshooting-fxserver-is-not-responding-how-to-fix\/","title":{"rendered":"D\u00e9pannage\u00a0: FXServer ne r\u00e9pond pas\u00a0! (Comment r\u00e9soudre ce probl\u00e8me)"},"content":{"rendered":"<p class=\"wp-block-paragraph\">Lorsque votre FXServer affiche des erreurs \u00ab\u00a0Pas de r\u00e9ponse\u00a0\u00bb, vous \u00eates g\u00e9n\u00e9ralement confront\u00e9 \u00e0 l&#039;un des cinq probl\u00e8mes principaux. Ce guide fournit des \u00e9tapes de d\u00e9pannage syst\u00e9matiques pour les administrateurs de serveur FiveM confront\u00e9s \u00e0 des probl\u00e8mes de connectivit\u00e9 entre txAdmin et FXServer.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cause principale\u00a0: incompatibilit\u00e9 de configuration des ports<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Probl\u00e8me<\/strong>: txAdmin ne peut pas se connecter \u00e0 FXServer en raison d&#039;une configuration de port incorrecte dans server.cfg<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>R\u00e9parer<\/strong>: V\u00e9rifiez que votre server.cfg contient les points de terminaison TCP\/UDP correspondants\u00a0:<\/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\">Remplacez les num\u00e9ros de port par ceux qui vous sont allou\u00e9s. Si les num\u00e9ros de port ne correspondent pas \u00e0 votre port d&#039;allocation principal, des erreurs de connexion se produisent.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>\u00c9tapes de validation<\/strong>:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>V\u00e9rifiez les param\u00e8tres txAdmin \u2192 FXServer pour les ports configur\u00e9s<\/li>\n\n\n\n<li>Comparer avec les d\u00e9clarations de point de terminaison server.cfg<\/li>\n\n\n\n<li>Red\u00e9marrer le serveur via la console apr\u00e8s les corrections<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Cause secondaire\u00a0: connectivit\u00e9 du moniteur txAdmin<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Probl\u00e8me<\/strong>: txAdmin:Monitor ne peut pas se connecter \u00e0 FXServer, ce qui provoque le message \u00ab FXServer ne r\u00e9pond pas ! \u00bb<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Causes profondes<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>FXServer ne r\u00e9pond pas au point de terminaison TCP (ressource bloqu\u00e9e)<\/li>\n\n\n\n<li>FXServer et txAdmin partageant le m\u00eame port TCP<\/li>\n\n\n\n<li>FXServer n&#039;\u00e9coute pas l&#039;interface locale<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>R\u00e9parer<\/strong>: Lancer FXServer en mode moniteur\u00a0:<\/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>Critique<\/strong>: N&#039;utilisez pas les arguments +exec lors du lancement de txAdmin. txAdmin n\u00e9cessite que FXServer s&#039;ex\u00e9cute en mode moniteur.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Interf\u00e9rence antivirus (Windows)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Probl\u00e8me<\/strong>: L&#039;analyse du r\u00e9pertoire FXServer par l&#039;antivirus Microsoft Defender provoque des d\u00e9marrages lents et des d\u00e9lais d&#039;expiration de la connectivit\u00e9<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>R\u00e9parer<\/strong>: Ajouter le r\u00e9pertoire FXServer \u00e0 la liste d&#039;exclusion\u00a0:<\/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=\"\"># Ex\u00e9cuter en tant qu&#039;administrateur Add-MpPreference -ExclusionPath &quot;C:\\FXServer\\&quot;\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Remplacez le chemin par l\u2019emplacement r\u00e9el de votre r\u00e9pertoire FXServer.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Probl\u00e8mes de configuration r\u00e9seau<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Probl\u00e8me<\/strong>: NAT\/passerelle masquant les ports sources UDP ou redirection de port incorrecte<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Liste de contr\u00f4le des correctifs<\/strong>:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Transf\u00e9rer les ports TCP et UDP dans le routeur\/pare-feu<\/li>\n\n\n\n<li>V\u00e9rifiez que le pare-feu Windows autorise FXServer.exe<\/li>\n\n\n\n<li>V\u00e9rifiez la configuration NAT pour la pr\u00e9servation du port UDP<\/li>\n\n\n\n<li>Tester la connectivit\u00e9 locale\u00a0: <code>telnet localhost 30120<\/code><\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Blocage des ressources au d\u00e9marrage<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Probl\u00e8me<\/strong>: Les ressources bloqu\u00e9es emp\u00eachent FXServer de r\u00e9pondre aux contr\u00f4les de sant\u00e9<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Approche diagnostique<\/strong>:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>D\u00e9marrer le serveur avec des ressources minimales<\/li>\n\n\n\n<li>Ajoutez progressivement des ressources pour identifier le coupable<\/li>\n\n\n\n<li>V\u00e9rifiez la console pour les messages d&#039;erreur de ressources<\/li>\n\n\n\n<li>Supprimer ou corriger les ressources probl\u00e9matiques<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Configuration de test de 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=\"\"># D\u00e9marrage minimal pour les tests, assurer le mapmanager, assurer le chat, assurer le spawnmanager # Ajouter d&#039;autres ressources une par une\n<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">D\u00e9pannage avanc\u00e9<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>\u00c9checs du contr\u00f4le de sant\u00e9<\/strong>: Le moniteur affiche \u00ab Erreur de demande HealthCheck\u00a0: connexion ECONNREFUSED \u00bb indiquant une perte de connectivit\u00e9 compl\u00e8te.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>\u00c9tapes de v\u00e9rification<\/strong>:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Confirmer l&#039;ex\u00e9cution du processus FXServer\u00a0: <code>liste des t\u00e2ches | findstr FXServer<\/code><\/li>\n\n\n\n<li>V\u00e9rifier la liaison du port\u00a0: <code>netstat -an | findstr :30120<\/code><\/li>\n\n\n\n<li><a href=\"https:\/\/fivemx.com\/fr\/comment-verifier-les-erreurs-dans-les-journaux-txadmin\/\">Consulter les journaux txAdmin <\/a>pour des mod\u00e8les d&#039;erreur sp\u00e9cifiques<\/li>\n\n\n\n<li>Tester avec un nouveau server.cfg en utilisant <a href=\"https:\/\/docs.fivem.net\/docs\/server-manual\/setting-up-a-server-vanilla\/#servercfg\" target=\"_blank\" rel=\"noopener\">configuration FiveM par d\u00e9faut<\/a><\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Note d&#039;incertitude<\/strong>:Certains probl\u00e8mes de connectivit\u00e9 peuvent provenir des configurations r\u00e9seau du fournisseur d&#039;h\u00e9bergement ou des politiques de pare-feu r\u00e9gionales qui ne sont pas imm\u00e9diatement apparentes dans les journaux du serveur.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Validation de la configuration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>\u00c9l\u00e9ments server.cfg requis<\/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=\"\"># Essentiel pour la liste des serveurs d\u00e9finit sv_projectName \u00ab\u00a0Votre nom de serveur\u00a0\u00bb d\u00e9finit sv_projectDesc \u00ab\u00a0Votre description de serveur\u00a0\u00bb # Configuration correcte du point de terminaison endpoint_add_tcp \u00ab\u00a00.0.0.0:30120\u00a0\u00bb endpoint_add_udp \u00ab\u00a00.0.0.0:30121\u00a0\u00bb # Activer l&#039;int\u00e9gration de txAdmin d\u00e9marrer txAdmin\n<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Les serveurs affichent des erreurs si sv_projectName et sv_projectDesc ne sont pas d\u00e9finis.<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Priorit\u00e9 de r\u00e9solution<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>D&#039;abord<\/strong>: V\u00e9rifiez la configuration du port dans server.cfg<\/li>\n\n\n\n<li><strong>Deuxi\u00e8me<\/strong>: Lancer FXServer sans arguments +exec<\/li>\n\n\n\n<li><strong>Troisi\u00e8me<\/strong>: Ajouter des exclusions antivirus<\/li>\n\n\n\n<li><strong>Quatri\u00e8me<\/strong>:V\u00e9rifiez les param\u00e8tres r\u00e9seau\/pare-feu<\/li>\n\n\n\n<li><strong>Cinqui\u00e8me<\/strong>: Isoler les ressources probl\u00e9matiques<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">La plupart des erreurs \u00ab FXServer ne r\u00e9pond pas \u00bb sont r\u00e9solues en corrigeant les incompatibilit\u00e9s de port entre les points de terminaison server.cfg et la configuration txAdmin, puis en garantissant des proc\u00e9dures de d\u00e9marrage du mode moniteur appropri\u00e9es.<\/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\/fr\/wp-json\/wp\/v2\/posts\/189713","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fivemx.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fivemx.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fivemx.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fivemx.com\/fr\/wp-json\/wp\/v2\/comments?post=189713"}],"version-history":[{"count":0,"href":"https:\/\/fivemx.com\/fr\/wp-json\/wp\/v2\/posts\/189713\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fivemx.com\/fr\/wp-json\/wp\/v2\/media\/189160"}],"wp:attachment":[{"href":"https:\/\/fivemx.com\/fr\/wp-json\/wp\/v2\/media?parent=189713"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fivemx.com\/fr\/wp-json\/wp\/v2\/categories?post=189713"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fivemx.com\/fr\/wp-json\/wp\/v2\/tags?post=189713"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}