Skip to main content

Error Codes

If the problem is not solved by the methods described below, please ask at the Mudfish Forum (https://forums.mudfish.net).

MUDEXP_00001​

Firewall bypass feature is currently disabled.

This message means that the mudfish disabled the authentication via the firewall bypass feature temporarily.

Normally it happens when Mudfish web site is under DDoS attack. Please don't use the firewall bypass feature. Or please use Mudfish under the environment where no the network firewall exists.

Unsuccessful response

This message means that the login request failed because the Mudfish web server returned an unsuccessful response.

MUDEXP_00023​

Failed to get information: (num)

This error can be caused by poor authentication with the mudfish authentication server. Depending on (num), its reason could be different. The reason for each (num) is as follows:

  • -1

    This code means that the TCP connection to the mudfish master server failed to establish due to some unexpected reason.

    Please check that there's a network firewall preventing the connection or try to change the network from WIFI to LTE/5G or LTE/5G to WIFI.

  • -2

    This can occur if the connection to the Mudfish Authentication Server is established, but the response cannot be received after sending authentication information.

    Usually, in this case, please check that there's a network firewall on your network that prevents you from connecting to the mudfish server, or if your personal firewall / antivirus program is blocking the connection.

  • -3

    This number indicates that your ID/PWD isn't correct or found. Please try to sign out and sign in again. To sign out, you can find a menu at the app configuration.

  • -9

    This number indicates that the authentication using the same ID was repeated several times within a short period of time so your connection was blacklisted by the authentication daemon.

    When this error occurs, please stop using the mudfish for a while and try connecting again after about 5 minutes.

  • -11

    The app could not save your login information on the Android device, for example because the storage path is on a read-only file system. Check whether completely uninstalling and reinstalling the app resolves the problem.

If the connection still fails after checking the firewall and trying both Wi-Fi and mobile data, send an Android problem report.

MUDEXP_00024​

Failed to do auto-login: <errno>

Automatic login failed. The reason depends on <errno>:

  • -1

    The app could not connect to the authentication server. A network firewall, an Android firewall app or another Internet connection problem may block it. Check Internet connectivity first. If the problem persists, contact support.

MUDEXP_00025​

Failed to fetch the staticnodes. (r <error_num>)

This message means that Mudfish app failed to fetch the information of mudfish nodes.

MUDEXP_00026​

Failed to get the default gateway for DNS (sid <sid>)

This issue means there's a problem to communicate with mudfish RTT server. When this issue happens, other mudfish error codes already are logged to show the details.

Please check that there's a network firewall between your phone and mudfish master servers. As temporary workaronds,

  • Please terminate the mudfish app completely and restart the mudfish app.

  • Or try to pick another mudfish node to use.

The selected node may also be unavailable. In that case, select another node.

MUDEXP_00034​

No mudfish credits available.

This error message indicates one of the followings:

  1. If your data plan is PPT (Pay-Per-Traffic), the issue is caused by lack of mudfish credits. Please purchase mudfish credits at https://mudfish.net/admin/credits/buy link.

  2. If your data plan is SUB (Subscription), normally you don't have buy the Subscription voucher. For details, please visit Policy change for Data Plan - 20210607 link.

MUDEXP_00035​

Can't use the mudfish node you picked.

In the case of this error, if you try to use the mudfish node picked in the mudfish app, but for some reason it can not be used, it could happen. It usually comes out for the following reasons.

  • If you have a Subscription data plan but no paid items are equipped.

    In this case, log in to https://mudfish.net and equip at least one paid item.

  • If the mudfish server is dead, this could happen. Then try to log out and log back in to the app to get the latest relay server information.

MUDEXP_00045​

Failed to read for auth (r <return_code> errno <error_code> <error_msg>)

This error means that it's successful to connect to the authentication server of Mudfish and send an information. <return_code> shows more details:

  • -1

    If <return_code> is -1, it means the mudfish authentication server doesn't response in time. Please check <error_code> <error_msg> to know the fundamental reason. <error_msg> could be one of the following:

    • EAGAIN (Try again)

      This means the authentication server is busy or taking too long to respond. Try again later.

MUDEXP_00046​

Failed to do auto-login: <errno>

This error message means Mudfish App failed to perform the auto-login due to <errno>. Each <errno> points:

  • -3

    This includes multiple meaning. Mostly, the token which used to perform the auto-login is no longer valid or expired.

MUDEXP_00049​

Failed to read for auth (r <return_code>)

This error means that it's successful to connect to the authentication server of Mudfish but failed to read the response. <return_code> shows more details:

  • -1

    If <return_code> is -1, it means the mudfish authentication server doesn't response in time.

MUDEXP_00065​

Failed to receive information from the master server for MS record: <rv> <errno> <errmsg>

This error points that it failed to fetch the mudfish nodes information from the mudfish master server. <errmsg> should point why it happens:

  • 115 Operation now in progress

    This error code normally points that the mudfish master server terminates the connection due to the timeout.

If you see this error continually, please log out the app and enable the network bypass feature at the sign in screen and test it again.

MUDEXP_00079​

talkc_open() fail.

This error indicates that there's a problem to connect to mudfish RTT daemon. Normally other error messages is already logged before showing this message.

MUDEXP_00086​

Failed to sync the configuration: <exception>

Configuration synchronization failed for the reason shown by <exception>:

  • java.net.SocketTimeoutException: communication with the Mudfish master server took too long, often because of a poor network connection.
  • java.net.UnknownHostException: the master server's domain name could not be resolved, which can also result from a network problem.

This message concerns configuration synchronization; it does not by itself mean that the Mudfish connection or your game connection has failed. You can disable configuration synchronization in the app settings to stop these messages.

MUDEXP_00099​

Failed to prepare VPN interface.

This error means that the Mudfish app is not prepared to create a VPN profile on the system or is revoked while creating a VPN profile.

Please check that you're using other VPN programs or running. Sometimes other VPN prgoram running triggers this issue.

MUDEXP_00113​

Problem setting up in-app billing: Response Code: <result_code>

This warning means that it failed to set up the in-app billing environment <result_code>

  • BILLING_UNAVAILABLE, Debug Message: Billing service unavailable on device.

    Problem

    This error indicates that a user billing error occurred during the purchase process. Examples of when this can occur include:

    • The Play Store app on the user's device is out of date.
    • The user is in an unsupported country.
    • The user is an enterprise user, and their enterprise admin has disabled users from making purchases.
    • Google Play is unable to charge the user's payment method. For example, the user's credit card might have expired.

    Possible resolution

    Automatic retries are unlikely to help in this case. However, a manual retry can help if the user addresses the condition that caused the issue. For example, if the user updates their Play Store version to a supported version, then a manual retry of the initial operation could work.

    If this error occurs when the user is not in session, retrying might not make sense. When you receive a BILLING_UNAVAILABLE error as a result of the purchase flow, it's very likely the user received feedback from Google Play during the purchase process and might be aware of what went wrong. In this case, you could show an error message specifying something went wrong and offer a "Try again" button to give the user the option of a manual retry after they address the issue.

MUDEXP_00120​

MUDEXP_00120: <exception>

At startup, the app tests whether a network firewall is present. One test checks access to https://mudfish.net/api/reqheaders. This error means that test failed.

  • javax.net.ssl.SSLHandshakeException: connection closed: the connection closed during the SSL handshake.

MUDEXP_00121​

Unexpected exception: <exception>: <reason>

The network firewall test could not access https://mudfish.net/api/reqheaders. The connection to the Mudfish website is not working correctly. See MUDEXP_00127 for exception details.

MUDEXP_00124​

Testing to mudfish.net:443 failed.

This error means that it failed to connect "mudfish.net:443". Due to this issue, the mudfish app enables the firewall bypass mode.

Please check your network has the network firewall which filters accesses to Mudfish.

MUDEXP_00127​

Unexpected exception: <exception>: <reason>

Automatic login failed. <exception> identifies the cause.

  • java.net.SocketTimeoutException with Read timed out: communication with the Mudfish master server or web server timed out.

Check your Internet connection and whether a network firewall blocks Mudfish.

MUDEXP_00137​

Unexpected exception: <exception_msg>

An exception occurred during login. A known exception is java.io.IOException, which indicates an input/output error during the connection attempt.

MUDEXP_00160​

tun -> server: Got <exception>

This error points that it failed to send UDP packet due to <exception> error. tun -> server means the app failed to send from tun(4) device to the remote socket. The following error codes are possible:

  • java.io.IOException: sendto failed

    • ENETUNREACH (Network is unreachable)

      This error indicates that the network is unreachable where Mudfish app tried to send UDP packet.

      Please check that your phone is accessing the internet first.

    • EPERM (Operation not permitted)

      This error indicates that sendto(2) operatioin for UDP (this UDP is used by the mudfish communicateion between app and mudfish node) is blocked by some reason.

      Please check you're using a firewall app on your phone or there's OS-dependent configuration to block mudfish.

MUDEXP_00208​

Failed to open .conf for writing at <path>: <errno> <errmsg>

The app could not write its configuration file to the phone's storage. <path> is the attempted location; <errno> and <errmsg> explain why it failed.

  • 30 Read-only file system: the app tried to write to a location that is not writable. Completely exit the app and try again. If this error occurs, report your phone model and Android version on the Mudfish forums or through private support.

MUDEXP_00245​

Unsuccessful response

This error means

  • Mudfish app detects that you're under the nework firewall because it failed to pass the firewall test.

  • With the firewall bypass mode enabled, Mudfish app failed to fetch the list of mudfish nodes from the mudfish master server via the cloudflare CDN proxy.

If you think the firewall test was false positive, you can manually turn off the firewall bypass mode at the sign-in screen.

MUDEXP_00246​

VSS_open(14.63.221.44:443) failed: <error_code> <error_number>.

Please check MUDEXP_00262 error link for details. This is triggered by the same reason mentioned in MUDEXP_00262 section.

MUDEXP_00251​

talkc__recv() error.

This error indicates that there's a problem to communicate between your phone and mudfish RTT daemon. Normally other error messages will follow up to point the detailed reason.

For talkc__recv() error: <errno> <errmsg>, error 11 Try again means a timeout: no data arrived from the Mudfish server within the expected time.

MUDEXP_00253​

VSS_open(14.63.223.218:443) failed: <error_code> <error_number>.

For this error code, please check the below MUDEXP_00262 error section. The reason is same.

MUDEXP_00262​

VSS_open(14.63.214.216:10010) failed: <error_code> <error_number>. Try next.

This error means that there's a problem to communicate between your phone and mudfish RTT daemon. <error_code> points more details:

  • 2 SELECT_TIMEOUT

    This means that there's no response from mudfish RTT daemon for a while. This could happen if 1) mudfish RTT daemon is down or 2) there's a network firewall which blocks the connections to Mudfish.

  • 4 CONNECT_ERROR

    This error means that it failed to perform connect(2) to the mudfish master server. <error_number> points why it failed to connect:

    • 101 ENETUNREACH

      Network is unreachable. By some unknown reason, the network is unreachble to the mudfish master server. Please check what kind apps you're running in the background.

MUDEXP_00263​

VSS_open(14.63.214.216:10009) failed: <error_code> <error_number>. Try next.

For this error code, please check the above MUDEXP_00262 error section. The reason is same.

MUDEXP_00266​

Failed to get a default SID... Something is wrong.

If this issue happens, please check your configuration whether you picked a mudfish node or not. Normally this message means that Mudfish app failed to find the configuration for the node.

This can also happen if the selected node is down, or if node information could not be retrieved from the master server because of an unstable connection or a firewall. Try another node, or completely exit and reopen the app.

MUDEXP_00267​

connect(2) fail: <errno> <err_string>

This warning means that it failed to calculate RTT (Round Trip Time) between your mobile phone and mudfish nodes using TCP protocol. Please check <errno> at below for details:

  • 101 Network is unreachable

    This code means the network is unreachable where Mudfish app tried to connect.

The full message may include the destination as connect(2) fail to <ip>:<port>: <errno> <errmsg>. <ip> is the node's IP address and <port> is usually 10007. For error 101, check that the phone can access the Internet and that the selected node is available.

MUDEXP_00292​

Failed to do the auto-login (reason <reason_code>)

This error means that the mudfish app tried to perform the auto-login but failed due to <reason_code> error. <reason_code> points

  • 4

    This reason code points that your authentication token is invalid or expired. You need to sign in again with your ID / password.

  • 5

    The authentication server blocked the login attempt. Stop trying briefly, then retry after about one minute.

MUDEXP_00350​

onPurchasesUpdated(<error_code>, <purchases>)

Fatal error during the API action. This is an internal Google Play error that may be transient or due to an unexpected condition during processing.

If this issue persists, please try to retry it again. <error_code> points the exact reason why:

  • BILLING_UNAVAILABLE = 3

    A user billing error occurred during processing. Examples where this error may occur:

    • The Play Store app on the user's device is out of date.
    • The user is in an unsupported country.
    • The user is an enterprise user and their enterprise admin has disabled users from making purchases.
    • Google Play is unable to charge the user's payment method.

    Letting the user retry may succeed if the condition causing the error has changed.

  • ERROR = 6

    Fatal error during the API action.

    This is an internal Google Play error that may be transient or due to an unexpected condition during processing. You can automatically retry (e.g. with exponential back off) for this case and contact Google Play if issues persist. Be mindful of how long you retry if the retry is happening during a user interaction.

For a persistent purchase error, completely exit and reopen the app. If it still fails, see Pricing for another payment method.

MUDEXP_00401​

Not enough information to calculate shortest pathes.

There is not enough RTT information from Mudfish nodes to calculate recommended routes. Check that your account has credits: node RTT tests may not work when no credits are available.