Error Code Reference

Note

Please leave a message at Mudfish Forums (http://mudfish.net/forums) if you can not find an answer.

This document describes about Mudfish Error Codes normally found at log files.

MUDEC_00022

CreateProcess failed with error <no>: <errmsg>

Are you using the latest Mudfish package? The reason of this error is that mudfish couldn’t find the default browser path of your OS or a path of cmd.exe. Please try with following examples:

  • Try to install ‘Chrome’ or ‘Firefox’ on your system and run. If they ask about setting the default browser, select ‘Yes’.
  • Or scan your system with anti virus.
  • If both solutions aren’t working, just open your browser then connects to http://127.0.0.1:8282
  • See Mudfish Launcher isn’t working.

MUDEC_00044

The client isn’t ready yet

This warning message indicates that the DHCP client of your OS wasn’t sending IP request with DHCP protocol. Normally this could happen if the firewall of OS blocks DHCP request to TAP-Win32 adapter v9 network device.

MUDEC_00045

The client doesn’t response with DHCP protocol

This error message is shown if your OS doesn’t make any DHCP request as client to Mudfish Core program. For these cases,

  • If you’re using v4.3.13 or above for Windows, you can try to use -I option for Mudfish Launcher letting it to use IP Helper APIs rather than DHCP to assign IPv4 address. To set it,

    • Moves “Mudfish Cloud VPN” menu from Start button.

    • Opens the property window of “Mudfish Launcher” icon.

    • Modify the command which found at “Target(T)” box that as default, the following value is set:

      “C:Program FilesMudfish Cloud VPNmudrun.exe”

    • Changes the command with -O option. For example, looks like below:

      “C:Program FilesMudfish Cloud VPNmudrun.exe” -I

  • If you’re using anti-virus or anti-malware programs, test after disabling the real-time monitoring services. For example, Norton Anti-virus program could block and drop DHCP Offer packets from Mudfish Core because it treats packets as part of ARP Spoofing.

  • Check TAP-Win32 adapter v9 network device which is a part of Mudfish Installer.

    • Sometimes DHCP feature is disabled by other VPN programs. For Mudfish, it must be enabled.
    • Check the device is enabled.

MUDEC_00049

no entry for SID

This issue could happen at the following scenarios.

  1. If a negative credit or no credit in your current account.
  2. If your equipped item is configured with invaild / dead relay server.
  3. If the relay server has internally ACL (Access Control List) and restrict your access.
  4. If the relay server information doesn’t be served by master server because of temporarily matter or permanently shutdown of the service.

MUDEC_00179

Path MTU is wrong.

In my personal opinion, if it doesn’t affect your game connection, it doesn’t require to be fixed. However if it affects, it could be little complicated:

To address this issue, you can check the following items:

  • Check your default MTU set on your network device driver. For example, if you tried or used a fast-pick kind of utilities before, these sometimes changed your MTU value forcibly without notificiation. With visiting the advanced option of each network drivier, you can check it.
  • Or tried to change the MTU value of TAP-Win32 adapter with smaller value. Its default value is 1500 (bytes). However it can try with small value (e.g. 1450, 1400, 1300 or a value you’d like to try).

MUDEC_00196

SID x isn’t alive

This message means that one of mudfish nodes whose SID is x and used by your configuration is down! So you need to check your Full VPN mode configuration if you enabled it because it’s currently pointing dead node so your traffic could detour another nodes.

MUDEC_00235

Too many heartbeat errors. Please check your firewalls.

This message points that your connections used for data path with mudfish nodes are continually encountering the delivery failure. Depending on your network environment, your connection is blocked by ISP or country (e.g. Great Firewall of China). Please check Firewall Issues link and try with different protocol or mac address.

Table Of Contents

Related Topics

This Page