Error 51 network is unreachable

error 51 network is unreachable

0.0 leads me to believe that DHCP is NOT enabled currently on the router. Check your router settings to ensure DHCP is enabled. If you want to. Then the network will be unreachable. In addition, this client tries only one `addrinfo` to connect and prefers ipv4 is the problem too. If both ipv4 and ipv6. The error is throw from here (using googleads for python) - I'm not clear the proxy is being used by urllib2 but don't want to try any rewiring without.

Error 51 network is unreachable - apologise, but

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

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

MUDEC_00001

Mudfish Launcher (mudrun) MUST be run as administrator

This error could happen if you're not running Mudfish Launcher as Administrator.

MUDEC_00002

Failed to connect to the master server.

This error points that it failed to connect to the mudfish master server for various operations.

If this error happens, you need to 'Status -> Process' menu to see "Core" log section. At that menu, please check there's an error or warning message because there's some messages to show the fundamental reasons.

MUDEC_00003

No TAP-Win32 Driver found.

TAP-Win32 adapter v9 network device is developed by OpenVPN Technologies, Inc and shipped with a part of Mudfish Cloud VPN.

My device isn't installed

Sometimes TAP-Win32 adapter v9 isn't properly installed even if the mudfish package try to install it automatically. To check whether it's installed or not

  1. Right click on the little computer screen next to your clock and click "Open Network and Sharing Center”
  2. then go to "Change Adapter Settings".
  3. Check there is a device called TAP-Windows-Adapter-V9.

If not, then you can try the following steps.

Workaround #1

  • Moves into the mudfish installation directory (normally ). At there you can find file.
  • Runs it as Administrator.
  • Install mudfish package again.

Workaround #2

You can install it manually by downloading tap-windows at https://openvpn.net/index.php/open-source/downloads.html link. Or you can try to install TAP-Win32 Driver as follows:

Workaround #3

  • Please check file too because it includes most detailed reason why your windows rejects the installation of TAP-Win32 adapter.

MUDEC_00012

Mudfish Launcher is already running.

This error means that on your system Mudfish Launcher is already running. Please check the system tray whether there is Mudfish Launcher icon. Or you can try to find mudrun.exe process with Task Manager.

MUDEC_00015

Failed to receive information from the master server for MR record:

This error means that Mudfish program failed to fetch mudfish node information from Mudfish master server. Depending , its meaning could be different:

  • ODR_ETIMEDOUT

    This error means that it failed to receive a data from master server within 5 seconds.

    It could be caused by

    • Some network firewall blocked a connection to Mudfish master server

    • Or a connection between your ISP and master server isn't stable.

    • Or Mudfish master server is busy.

You should restart Mudfish program again to fix this problem. If you think this issue is caused by blocking of network firewall, you can try to see Firewall Issues - Mudfish Master Server.

MUDEC_00016

Failed to receive information from the master server for MR record:

This issue is same error with MUDEC_00015. Please check MUDEC_00015 for details.

MUDEC_00018

failed to receive information from the master server:

This error means it failed to get the response from the mudfish master server for authentication. and <err_string> represent details about why this issue happens.

You can check Firewall Issues - Mudfish Master Server section for workarounds.

MUDEC_00022

CreateProcess failed with error :

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_00026

Wrong syntax on .conf file

This error means there's wrong syntax on file which is the configuration file for Mudfish Launcher. To solve this issue, please delete file which found at the mudfish installation directory and restart the mudfish.

MUDEC_00031

TOL_connect(, ) failed:

This error message happens if you enabled FastConnect mode. By unknown reason, it means it failed to connect and via mudfish node you'd picked.

If is 8081, it means that it failed to access SOCKS proxy. So as workaround,

  1. You can try to disable FastConnect mode

  2. Or you can try to change mudfish node you'd picked to another.

If is 8085, it means that it failed to access the TUNNEL proxy internally. shows details why it failed:

  • 64 Host is down

    This error means that there's no routing path to in mudfish core. Normally this issue means there's a problem to communicate with mudfish nodes you picked.

    Please try to change a mudfish node from one to another. If it still shows these error, please send us Problem Report.

MUDEC_00043

Failed to write the routing socket message for /// ()

This error means it failed to write (insert or delete) the routing table entry in Mudfish core process due to reason. Most common error messages are as follows:

  • No such process

    This means it could not delete the routing table entry because there's no matching entry.

    This is normally not harmful so you can ignore.

  • Network is unreachable (51)

    This error means that there's a routing table problem to reach to the mudfish node you'd picked.

    Please check the mudfish core process log at 'Status -> Process' menu to see the full errors. And please check there's another error before this error too.

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.

To see workarounds, please refer MUDEC_00045 because it's caused by same reason.

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 Windows 10, sometimes this issue is caused by Windows because it doesn't actively try to lease private IP address from TAP-Win32 adapter v9 network device.

    • Please open 'Task Manager'.

    • Or please try to keep "Change Adapter Settings" window open as follows:

      1. Right click on the little computer screen next to your clock at system tray.

      2. Click "Open Network and Sharing Center"

      3. Then click "Change Adapter Settings".

      4. Done! Just keep the window open.

  • If you're using v4.3.13 or above for Windows, you can try to use 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 Files\Mudfish Cloud VPN\mudrun.exe"

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

      "C:\Program Files\Mudfish Cloud VPN\mudrun.exe" -I

    • If this option is applied properly you can find a log as follow from Mudfish Core process which found at "Status → Process" menu::

      [INFO] Setting IP address (ip) with IP Helper.

  • 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.

    • If IPv6 is enabled for TAP-Win32 adapter v9 network device, please disable it completely. Sometimes this solves the problem.

MUDEC_00049

no entry for SID

This issue could happen by multiple reasons as follows:

  1. If you just bought the mudfish credit, you need to restart the mudfish program completely. Sometimes you can encounter this issue when you try to connect a mudfish node without restarting the problem.

  2. If your data plan is "Subscription", you need to equip the Subscription voucher. Please check it at http://mudfish.net/admin/user/dataplan/modify link.

  3. If a negative credit or no credit in your current account.

  4. If your equipped item is configured with invaild / dead mudfish node.

  5. If the mudfish node information doesn't be served by master server because of temporarily matter or permanently shutdown of the service.

  6. If you limits the list of mudfish nodes at 'Setup -> Nodes' menu, sometimes this issue could happen. To solve this issue, you can clear the list limitation.

MUDEC_00051

Failed to set the default route.

This error means that it failed to set the default route internally for mudfish core program. Normally it's caused that it failed to fetch the mudfish node information or not permitted by various reason. For most of cases, it's related with mudfish credit.

  • Please check your account has a mudfish credit.

  • If your data plan is Subscription based, please make sure that at least one paid item is equipped.

MUDEC_00059

ODR_write() error to : <err_num>

This error means that it failed to send the data via mudfish node whose public IP is because it encountered . The details about error messages are as follows:

  • ODR_ENOTCONN

    It failed to connect to the mudfish node due to failure of TCP handshake.

  • ODR_EAGAIN

    This error means that the connection isn't established yet but it tried to send the data to the mudfish node.

    If this issue is always happening, please try to change a mudfish node to another one.

If this error happens, please try to change the mudfish node or Connection Protocols.

MUDEC_00062

ODR_read() for hdr error from :

This error means that a connection between your desktop and mudfish node you used is aborted by reason. The details about error messages are as follows:

  • ODR_ECONNABORTED

    The virtual circuit was terminated due to a time-out or other failure. The application should close the socket as it is no longer usable.

  • ODR_ECONNRESET

    The virtual circuit was terminated by the reset packet from the mudfish node (peer). It means the connection between mudfish node and your desktop is corrupted or there's a problem at mudfish node side. Normally this issue isn't from your side. It could be a problem of the mudfish node you'd picked.

    Please try to use other mudfish nodes.

  • ODR_ETIMEDOUT

    The connection has been dropped, because of a network failure or because the system on the other end went down without notice. Normally this error means that mudfish node doesn't send any packets to you anymore.

MUDEC_00064

ODR_read() for payload error from : "

Please check MUDEC_00062 error link for details because it's from the same reason.

MUDEC_00066

ODR_recvfrom() error from :

This error means that it failed to receive the data from . This IP points the public IP of mudfish node you used. You need to check the error number and message for details:

  • 10090 ODR_EMSGSIZE

    This points that the message was too large to fit into the buffer pointed to by the mudfish and was truncated. This error isn't a common because the received data is over MCLBYTES (normally it's around 2 KB).

    If you stil encounter this issue, please consider to change Connection Protocols to TCP-based one.

MUDEC_00079

Failed to connect the master server ::

This error means that you can't connect to the master server using :. Are you under network firewall? If then it could be possible if the firewall blocks an access to mudfish sites.

For this case, please check Mudfish Master Server link for details how to avoid.

MUDEC_00080

TOL_sendto(2) error to <device_name> <private_ip> for heartbeat. ()

Why?

This error message means it failed to send a heartbeat packet to the target mudfish node .

However if its error level is "[INFO]" not "[ERROR]", you can ignore this error message because it doesn't affect your connection

Solution

  • Please try to change a mudfish node to others

  • Or please try to change "Connection Protocol" found under "Setup → Program" menu.

  • Or please contact to the mudfish forums.

MUDEC_00086

ReadFile() error (handle <handle_no>):

This error is related with TAP-Win32 adapter v9 network adapter when it failed to do 'read' operation. For details, and shows the detailed message about why:

  • 2 The system cannot find the file specified.

    This message means that it failed to find a file associated with TAP-Win32 adapter v9 adapter. This error could happen when some other processes aborted the network adapter forcibly.

MUDEC_00124

CreateIpForwardEntry() failed:

This error means that Mudfish core process failed to insert the routing path into your host OS. and points an exact reason of this failure. Known error messages are as follows:

  • One or more arguments are not correct.

    This error means it passed the invalid arguments for calling CreateIpForwardEntry() function. If you encounter this issue, please send Problem Report for details.

MUDEC_00126

ODR_CreateIpForwardEntry failed: IP // (ifindex metric )

This error means that it failed to create the forwarning entry (routing table) for Windows. Please check 'Status → Process' menu for previous errors first. Normally you can see MUDEC_00124 error before this error which shows a reason error message.

MUDEC_00129

ODR_CreateIpForwardEntry failed: IP // (ifindex <interface_index> metric <metric_value>)

This error means that Mudfish core process failed to insert the routing path (, and ) into your host OS.

MUDEC_00137 (router)

ODR_writev() error:

If points ODR_EIO, please ignore this error message because it's not harmful.

MUDEC_00139

ODR_read() error:

This error means that it failed to read a data from tap(4) driver (in Windows, it's called as TAP-Win32 adapter v9). and points details:

  • 10011 ODR_ENOENT

    Please check MUDEC_00086 error section and see '2 The system cannot find the file specified.' entry for details.

MUDEC_00145

udp_relay: TOL_sendto(2) failed to <private_ip>: <error_num> <error_msg>

This error could happen if you're using FastConnect mode. It indicates that it failed to send packets to mudfish node whose private IP is <private_ip> due to <error_msg>.

  • No buffer space available

    It means too many connections are made from your desktop to Mudfish so no more resources are available to keep the connections.

  • Host is down

    It means the connection between your desktop and mudfish node you'd picked isn't established yet.

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_00180

TCP_socket(2) failed: <err_string>

This error could happen if you enabled FastConnect mode. Depending on number, its reason could be different:

  • 55 No buffer space available

    This message means that Mudfish program could not create a TCP socket anymore due to out of resources allocated for program. This message caused by that your desktop created too many connections to the internet.

    Please check the following things:

    • If Full VPN mode is enabled, please turn off if it's not required.

    • Or please terminate any other programs cause the network traffics or connections.

MUDEC_00186

Wrong TCP format hdr:

This error means that your connection is something wrong to communicate with mudfish node you'd picked. Or your connection is monitored and filtered by network firewalls.

You can try to use other Connection Protocols or change a mudfish node.

MUDEC_00192

Failed to open '/dev/tap7': <err_string>

Depending on code, the fundamental reason could be different. Please check the following lists.

  • Please use latest Mudfish version available at https://mudfish.net/download link. No longer tuntap driver is used for Mac OS X.

  • Sometimes this issue is caused by that already mudfish process is running. Please check 'mudfish' process is running and kill it.

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.

MUDEC_00238

Packet loss rate to

This message means that you're using for mudfish configuration but mudfish found that your connection between your desktop and mudfish node you picked is unstable. points the name of mudfish node you selected. points the packet loss rate. To solve this issue, you should:

  • If you're familiar with WinMTR, please check How to use WinMTR link and test to the public IP of mudfish node you picked. The public IP of mudfish node is found at http://mudfish.net/server/status link.

    It'll show where this packet loss is from.

  • Please check your ISP first. Sometimes this issue could be caused by your ISP side.

  • If your ISP works fine, please try to change mudfish node to another. Sometimes this could be helpful to solve this issue.

MUDEC_00254

authc_read() failed:

This issue points that it failed the configuration information from the mudfish master server. So it means that there's a problem to communicate with the master server.

You need to check Firewall Issues - Mudfish Master Server section for workarounds.

MUDEC_00258

Failed to fetch the configuration.

This error is same one with MUDEC_00254.

MUDEC_00262

ODR_sendto() error to <ip_addr> Message too long. Check your path MTU. (curmtu buflen

This error means there is a MTU (Maximem Transmission Unit) error from your desktop to mudfish node you're using whose IP address is <ip_addr>.

Workaround #1

This workaround is recommended rather than workaround #2 not to lose any performance. To fix this problem, you should modify MTU value of TAP-Win32 adapter v9 network adapter and follow these steps:

  1. Open Network Connections by clicking the Start button, and then clicking Control Panel. In the search box, type adapter, and then, under Network and Sharing Center, click View network connections.

  2. Right-click TAP-Win32 adapter v9 connection, and then click Properties. Administrator permission required If you're prompted for an administrator password or confirmation, type the password or provide confirmation.

  3. Click Configure button at Networking tab.

  4. At Advanced tab, you can find MTU property. So you can reduce its value (e.g. 1400, 1300 and etc) from 1500 (default value) until this message is gone.

Workaround #2

Sometimes this issue is solved by changing the connection protocol from UDP to TCP.

  1. Visits 'Setup → Program' menu.

  2. Changes to TCP based protocol / port.

MUDEC_00269

udp_relay: TOL_sendmsg(2) to : failed:

This error message is shown only if you turned on FastConnect mode. This shows that it failed to send a UDP packet to : through Mudfish. represents a detail reason as follows:

  • 55 No buffer space available

    This means no more buffer space on UDP socket used by UDP proxy of Mudfish. Normally it points that there's a problem to communicate with mudfish node.

    To solve this problem:

    • You can try to turn off FastConnect mode.
    • Or you can try to use other mudfish nodes.
    • Or you can try to change the connection protocol to another.

MUDEC_00279

arp:

This error means that something is wrong at Mudfish services. Please contact to us via Mudfish Forums to fix this.

MUDEC_00281

Failed to fetch the routing table.

This error means Mudfish failed to receive the routing table information from master server. Sometimes it could be failed due to network issue but if it keeps persistent, please try to follow below:

MUDEC_00282

Failed to receive heartbeat resp -1

This error means Mudfish failed to receive a heartbeat response from the master server. Sometimes it could be failed due to network issue but if it keeps persistent, it means one of followings:

  • Network Firewall could block your connection.

  • A connection between your ISP and mudfish master server isn't stable.

MUDEC_00285

CryptAcquireContext failed with error :

This issue could happen while Mudfish try to check the permission of creating the encryption key.

  • 0x80090024 The profile for the user is a temporary profile

    Please check MUDEC_00286 section for workarounds.

MUDEC_00286

MUDEC_00286: CryptAcquireContext, newkeyset failed with error:

This error could happen at very beginning while Mudfish Launcher is executed. It means it failed to initialize the random key generator using current your account. Normally this issue happens because the password for account isn't set. To solve this problem you can try to

  • Create an other user account for Windows OS then try with it.

  • Or set a password for current user's password.

MUDEC_00305

Failed to receive information from the master server for MR record:

This error means that it failed to fetch the information of mudfish nodes from mudfish master server.

points the reason about why this issue happens:

  • ODR_ETIMEDOUT

    This message means that receiving the data was timed out. So it means the master server didn't respond or there's other network error due to network firewall.

To solve this problem you can try to

  • Checks Firewall - Mudfish Master Server document if you feel the connection blocked by network firewall.

  • Use other mudfish nodes or restart the mudfish problem.

MUDEC_00306

Failed to receive information from the master server for MS record:

This issue is same error with MUDEC_00305. Please check MUDEC_0030t for details.

MUDEC_00309

Failed to write the routing socket message:

This error means that it failed to add the rouing table entry in the mudfish core. and indicate why it was failed. Here's detailed error messages:

  • 51 Network is unreachable

    This error means it's not possible to connect the mudfish node you'd picked. For this case, please try to change a mudfish node from one to another.

MUDEC_00314

Failed to get any OS level event for reconnecting.

This error means that Mudfish back-end virtual driver couldn't get any events from OS (Windows / Windows / Mac OS X) regarding to the connection. This issue could happens if your network firewall on desktop or other network blocks the connection between your desktop and mudfish node you'd picked.

To solve this problem you can try to do

  1. Try to use other mudfish nodes.

  2. Or change Connection Protocols to another.

MUDEC_00316

Failed to receive information. / /

This error message means that you failed to get the routing table information after authentication.

MUDEC_00319

Failed to authenticate using ID/PWD

This error means that it failed to authenticate using your current username and password.

However if your password works to visit the mudifish web site but doesn't work with Mudfish Launcher, please visit http://accounts.en.loxch.com and try to change your password to simple combination. Then try it again.

MUDEC_00320

Failed to fetch the static node information.

This error means that it failed to fetch the static node information from the mudfish master server. For most of cases this error could happen by one of the followings:

  • When the connection between your ISP and mudfish master server is unstable.

  • Or when something blocks the connection to the mudfish master server.

  • Or your OS system has a wrong winsock setup.

To solve this problem, please try the followings:

MUDEC_00330

Slowed down due to speed limitation.

This error is caused by that your data plan is Subscription. At Subscription it has a speed cap so your traffics could be dropped by mudfish program if its limitation is hit.

To solve this problem, you can try one of the following things:

  1. You can try to change your data plan to PPT (Pay Per Traffic).

  2. Or terminate the program making network activities to reduce the network traffic usage.

  3. Or you can upgrade your voucher type for Subscription data plan. For details, you can visit https://mudfish.net/admin/user/dataplan/modify link.

MUDEC_00333

Failed to fetch static node information.

This error means it failed to lease IP address to communicate with a node link. When this issue still happens, please visit 'Status → Process' menu to see the core logs. It'll show other error or warning messages which happened before this error.

MUDEC_00338

Failed to receive a data. (res / )

This error points that it failed to receive a data from the mudfish master server. It means that it tried to read but failed with .

When this issue still happens, please visit 'Status → Process' menu to see the core logs. It'll show other error or warning messages which happened before this error.

MUDEC_00350

Failed to connect to the mudfish master server.

This error means that it failed to connect to the master server of mudfish for authentication. Please check 'Status -> Process' menu to see the core logs. You can find other error or warning level messages before this code.

MUDEC_00351

Failed to recvfrom(2) the data from master server. Error

This error means it failed to connect to the master server of Mudfish for authentication.

MUDEC_00357

Your account isn't activated.

This error means that the mudfish authentication server blocks your connection because too many tries for ID/PWD authentication within 1 minutes.

Please check your browser or mudfish programs whether it does wrong or not. So please wait around 5 minutes and try to login again.

MUDEC_00405

VSS_open(:) failed:

This error means you failed to connect :. The reason depends on as follows:

  • 2 (SELECT_TIMEOUT)

    This means that the connection was timed out. For most of cases, this issue is caused by the network firewall.

  • 5 (GETADDRINFO_ERROR)

    This means that it failed to perform DNS resolving for the domain. Sometimes this issue could happen your DNS requests are inspected by network firewall.

MUDEC_00409

Failed to connect the RTT server.

This error means that it failed to connect to the master server of mudfish for RTT information. Please check 'Status -> Process' menu to see the core logs. It'll show more details about why.

MUDEC_00410

Failed to connect the master server.

This error means that it failed to connect to the master server of mudfish for authentication. Please check 'Status -> Process' menu to see the core logs. It'll show more details about why.

MUDEC_00414

Failed to connect due to .

This error points that mudflow (Mudfish Flow Controller) process failed to connect . Normally points the private IP address of mudfish node you picked. points the specific reason why it failed:

  • WSAEACCES

    This error means your Windows OS blocks the connection. For most of cases it's caused by AV (Anti Virus) program.

    Please try to add mudfish processes as follows to the exceptional list:

    • mudfish.exe
    • mudflow.exe
    • mudrun.exe

MUDEC_00415

Failed to connect (errno )

This error points that it failed to connect to set up the configuration for Advanced Node / MultiPath Node settings. Normally is the private IP and port of mudfish node you'd picked.

indicates the reason:

  • 10053 (WSAECONNABORTED)

    An established connection was aborted by the software in your host machine.

    Are you using AV (anti-virus) / firewall program? Please check that those are blocking a connection of mudfish first.

    This message indicates that the connection is aborted by the software you're using on your box.

  • 10065 (WSAEHOSTUNREACH)

    No route to host. A socket operation was attempted to an unreachable host.

If this issue happens, please try to change a mudfish node setting to another combination.

MUDEC_00416

Failed to connect to : (errno )

This error points that it failed to connect to set up the configuration for Advanced Node / MultiPath Node settings. Normally is the private IP and port of mudfish node you'd picked. This error is like MUDEC_00415 but this is happening on Linux or Mac OS X environments.

indicates the reason:

  • Mac OS X

    • 60 (ETIMEDOUT)

      Operation timed out. It tried to connect but failed within the timeout.

MUDEC_00421

No mudfish nodes picked for the advanced node for the item

This error points that it failed to pick a mudfish node which used for advanced mode or multipath mode. For most of cases, it's related with "Auto Select" option for mudfish node pick-up.

To solve this problem:

MUDEC_00424

RTT stddev values are over 15% of your RTT avg to the closest mudfish nodes. Please check your ISP whether there's an issue or network congestion.

This error indicates the RTT standard deviation is more than 15% of the mean value while performing RTT calculcation internally.

If you see this message, it means that the connections to mudfish nodes closest to your current location are unstable. The detailed calculation formula is:

  1. Picks 6 mudfish nodes closest to the current user among all mudfish nodes and periodically performs RTT calculation.

  2. If all six checked mudfish nodes show an RTT stddev (standard deviation) of more than 15% of the RTT avg (average), a warning message is displayed.

If this error persists, please check the following things:

  • Do you use wireless connection (WIFI) rather than the LAN cable to connect the internet? If you're using WIFI, RTT stddev could be affected by the strength of WIFI signals.

  • Check your ISP or check whether you have internal QoS or firewall settings.

MUDEC_00440

recv(2) error: read error

This error means that it failed to receive the data from the mudfish master server or nodes. The reason depends on :

  • 10060 WSAETIMEDOUT

    This message means that receiving the data was timed out. So it means the master server didn't respond or there's other network error due to network firewall or other reason.

MUDEC_00446

Give up to wait the snode backed for SID

This error means that the mudfish flow controller (mudflow.exe) can't find a mudfish node information you set. If you see this mesagee, you can check the following things:

  • Checks your mudfish credits. Sometimes this issue is caused by out of mudfish credits.

  • Or visit 'Setup -> Nodes' menu and clear your limitation for picking the mudfish nodes. Sometimes this issue is caused by mismatch of mudfish node information between the mudfish flow controller and the mudfish core.

  • Or if all other things are fine but this issue still happens, please check Mudfish Master Server link and consider to test with option.

MUDEC_00463

Failed to send to the routing information (localip errno )

This error points that it failed to send the routing table information to the mudfish node you'd picked for Advanced Node Mode. If this issue persists, you can try to change the node mode from Advanced Mode to Basic Mode or Multi-Path Mode.

indicates why this error happens:

  • 10054 (WSAECONNRESET: Connection reset by peer)

    An existing connection was forcibly closed by the mudfish node. Normally it means that there's a problem to connect.

MUDEC_00464

AddIPAddress() failed:

This error could happen if you're using option for mudfish launcher. Depending on , it could mean different reasons as follows:

  • 5010 (ERROR_OBJECT_ALREADY_EXISTS)

    This error code means there's already a exisiting object to TAP-Win32 network v9 adapter. So you can ignore if mudfish works fine.

MUDEC_00467

Failed to recvfrom(3) the flush information (received / expected / errno / sid )

This error means that it failed to receive the data from the mudfish node you're using. The reason depends on :

  • 10060 WSAETIMEDOUT

    This message means that receiving the data was timed out. So it means the master server didn't respond or there's other network error due to network firewall or other reason.

MUDEC_00470

Increasing no of fragmented packets.

If the issue is still happening, it means that current network device (NIC) is constantly receiving fragmented packets. You can ignore this error message if you don't have any problems to use mudfish. However the packet loss rate could be affected by fragmented packet.

It is recommended to resolve the issue as much as possible because it increases.

Usually, one of the followings can cause this issue:

  • MTU (Maximum Transmission Unit) of NIC network device has an unusually small value.

  • If MTU value used for communication with the mudfish nodes is larger than expected, this issue could happen.

Please check the following list to resolve this issue.

  1. Check MTU (Maximum Transmission Unit) of currently installed network devices. For ethernet its default value is 1500. If it's more smaller, you can reset to the default value.

  2. If you enter the mudfish UI 'Settings -> Program' menu, there is an MTU menu. Try setting this value to 1400 (the mudfish default) or 1300.

MUDEC_00477

Too big UDP packet to send.

This error means that your game client is trying to send a bigger UDP packet than what mudfish could handle.

Please visit 'Setup -> Program' menu and adjust your MTU with lowering the value. For example, you can try to test with the following values:

MUDEC_00496

WSAIoctl() failed: error retbytes

This error means the redirect record associated with the socket failed to fetch. indicates more details:

  • 10022 (WSAEINVAL)

    Normally this error means the mudfish kernel driver for windows filtering platform is conflict with other AV (anti-virus) or firewall programs.

    Please check that on your machine there's a program which could intercept your connection and do something. If there's one, you can try to uninstall it and test it again.

    As a workaround, you can try

    • Turn off WFP Item mode.

      This will disable WFP feature of mudfish and no longer you will encounter this issue.

    • If you still want to use WFP Item mode, you can send us the result of from Command Prompt to check which the kernel drivers are loaded.

MUDEC_00501

bind failed with error:

This error means that it failed to bind a socket with specific IP:port for listener. The explains why:

  • 10048 WSAEADDRINUSE

    Only one usage of each socket address (protocol/network address/port) is normally permitted.

    Please make sure that all mudfish processes are restarted properly. Normally this error points that a mudfish process is already running.

MUDEC_00514

StartService() failed:

In the case of this error, it means that the windows service for Mudfish WFP (Windows Filtering Platform) driver did not run properly. The detailed reason depends on the value of .

  • 0x7f (ERROR_PROC_NOT_FOUND)

    In this case, there can be two cases.

    1. This may occur if the mudwfp.sys driver is not installed properly. Please check if the mudfish package was installed properly and there were no errors during the installation process.

    2. Or, if the Windows version you are using is 7 or lower. For the WFP feature, it must be at least Windows 8 or higher to work properly.

MUDEC_00539

Checking RTT to mudfish nodes are failing. Are you under network firewall?

When mudfish is launched, the program measures RTT (Round Trip Time) between your desktop and mudfish nodes. This error indicates that the RTT measurement is failed or RTT is relatively high (above 1.5 secs).

Please check that you're under network firewall. And try to change 'RTT Checking Method' found at 'Setup -> Program' menu.

MUDEC_00546

NetworkExtension isn't ready yet

This error means that mudfish core process didn't get any responses from mudfish NetworkExtension module. Please check two things first:

  • Check that VPN Configuration for mudfish is installed properly.

  • System Extension module for mudfish is installed properly. You should explicitly enable the systemextension module for mudfish.

To solve this issue, please try to uninstall mudfish completely and try to reinstall mudfish from the scratch. You can check the following links:

MUDEC_00555

Failed to sendto the ping information. (errno )

This error means you're using "Advanced Node mode" for the game item settings but failed to send a ping probe to the mudfish nodes you're using. indicates details why:

  • 10054 (WSAECONNRESET)

    Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close. This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress.

MUDEC_00556

Failed to connect mudfish short_path server.

This error indicates that mudfish program can't access to domain using TCP 10012 to get the recommended routing path. Please check 'Status -> Process' menu to see the detailed error reason.

In the log file, other error messages will exist.

MUDEC_00567

vhttp_rxhdr error.

This error indicates that mudfish program failed to parse HTTP response header got from the server specified. Please check 'Status -> Process' menu to see the detailed error reason.

In the log file, other error messages will exist.

MUDEC_00572

VHTTP_rxbody error.

This error indicates that mudfish program failed to send HTTP POST request to the server specified. Please check 'Status -> Process' menu to see the detailed error reason.

In the log file, other error messages will exist.

MUDEC_00586

recv(2) error: read error

This error points that there's a problem to receive the data from mudfish master server or mudfish RTT server. indicates the detailed reason:

  • 10060 (WSAETIMEDOUT)

    Connection timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.

If this issue still happens, please check Mudfish Master Server link and consider to test with option.

MUDEC_00724

ODR_read() for hdr error from :

This error points that one of the brokers for Multi-Path support encountered an error. If you don't have a problem with your game connection, you can ignore this issue.

  • This is a public IP of mudfish node which Multi-Path broker used.

  • Please check MUDEC_00062 error link for details because it's from the same reason.

MUDEC_00729

ODR_read() for payload error from : "

Please check MUDEC_00062 error link for details because it's from the same reason.

MUDEC_00748

No DHCP enabled for TAP-Win32 adapter v9

In case of this error, it means that DHCP setting is not enabled for the TAP-Win32 adapter v9 device installed in the system when Mudfish is installed.

To resolve this issue, please do the following:

  • Go to Control Panel -> Network and Internet -> Change adapter options menu.

  • From there, open the properties window of the TAP-Win32 adapter v9 device.

  • Open the properties of the 'Network -> Internet Protocol Version 4 (TCP/IPv4)' item.

  • Then enable the "Obtain an IP address automatically" function there. Also enable "Obtain DNS server address automatically".

After doing this, restart the mudfish completely and the problem will be solved.

MUDEC_00800

Due to too much data used in this month, your speed cap is more limited.

If your data plan is Subscription, this issue could happen when the monthly maximum usage of the subscription voucher is exceeded.

For detailed usage limits, please refer to Data Plans link.

In the case of network errors (e.g. a connection to a proxy server fails) Proxifier outputs error code numbers. These are the standard error codes. This section contains the codes of network errors and their description.

EPERM1Operation not permittedENOENT 2 No such file or directory ESRCH 3 No such process EINTR 4 Interrupted system call EIO 5 Input/output error ENXIO 6 Device not configured E2BIG 7 Argument list too long ENOEXEC 8 Exec format error EBADF 9 Bad file descriptor ECHILD 10 No child processes EDEADLK 11 Resource deadlock avoided ENOMEM 12 Cannot allocate memory EACCES 13 Permission denied EFAULT 14 Bad address ENOTBLK 15 Block device required EBUSY 16 Device / Resource busy EEXIST 17 File exists EXDEV 18 Cross-device link ENODEV 19 Operation not supported by device ENOTDIR 20 Not a directory EISDIR 21 Is a directory EINVAL 22 Invalid argument ENFILE 23 Too many open files in system EMFILE 24 Too many open files ENOTTY 25 Inappropriate ioctl for device ETXTBSY 26 Text file busy EFBIG 27 File too large ENOSPC 28 No space left on device ESPIPE 29 Illegal seek EROFS 30 Read-only file system EMLINK 31 Too many links EPIPE 32 Broken pipe EDOM 33 Numerical argument out of domain ERANGE 34 Result too large EAGAIN 35 Resource temporarily unavailable EWOULDBLOCK EAGAIN Operation would block EINPROGRESS 36 Operation now in progress EALREADY 37 Operation already in progress ENOTSOCK 38 Socket operation on non-socket EDESTADDRREQ 39 Destination address required EMSGSIZE 40 Message too long EPROTOTYPE 41 Protocol wrong type for socket ENOPROTOOPT 42 Protocol not available EPROTONOSUPPORT 43 Protocol not supported ESOCKTNOSUPPORT 44 Socket type not supported ENOTSUP 45 Operation not supported EPFNOSUPPORT 46 Protocol family not supported EAFNOSUPPORT 47 Address family not supported by protocol family EADDRINUSE 48 Address already in use EADDRNOTAVAIL 49 Can't assign requested address ENETDOWN 50 Network is down ENETUNREACH 51 Network is unreachable ENETRESET 52 Network dropped connection on reset ECONNABORTED 53 Software caused connection abort ECONNRESET 54 Connection reset by peer ENOBUFS 55 No buffer space available EISCONN 56 Socket is already connected ENOTCONN 57 Socket is not connected ESHUTDOWN 58 Can't send after socket shutdown ETOOMANYREFS 59 Too many references: can't splice ETIMEDOUT 60 Operation timed out ECONNREFUSED 61 Connection refused ELOOP 62 * Too many levels of symbolic links ENAMETOOLONG 63 File name too long EHOSTDOWN 64 Host is down EHOSTUNREACH 65 No route to host ENOTEMPTY 66 Directory not empty EPROCLIM 67 Too many processes EUSERS 68 Too many users EDQUOT 69 Disc quota exceeded ESTALE 70 Stale NFS file handle EREMOTE 71 Too many levels of remote in path EBADRPC 72 RPC struct is bad ERPCMISMATCH 73 RPC version wrong EPROGUNAVAIL 74 RPC prog. not avail EPROGMISMATCH 75 Program version wrong EPROCUNAVAIL 76 Bad procedure for program ENOLCK 77 No locks available ENOSYS 78 Function not implemented EFTYPE 79 Inappropriate file type or format EAUTH 80 Authentication error ENEEDAUTH 81 Need authenticator EPWROFF 82 Device power is off EDEVERR 83 Device error, e.g. paper out EOVERFLOW 84 Value too large to be stored in data type EBADEXEC 85 Bad executable EBADARCH 86 Bad CPU type in executable ESHLIBVERS 87 Shared library version mismatch EBADMACHO 88 Malformed Macho file ECANCELED 89 Operation canceled EIDRM 90 Identifier removed ENOMSG 91 No message of desired type EILSEQ 92 Illegal byte sequence ENOATTR 93 Attribute not found EBADMSG 94 Bad message EMULTIHOP 95 Reserved ENODATA 96 No message available on STREAM ENOLINK 97 Reserved ENOSR 98 No STREAM resources ENOSTR 99 Not a STREAM EPROTO 100 Protocol error ETIME 101 STREAM ioctl timeout EOPNOTSUPP 102 Operation not supported on socket ENOPOLICY 103 No such policy registered ELAST 103 Must be equal largest errno

QIIME 2 Forum

(qiime2-2020.8) Rui-Mac:~ rui$ redbiom summarize contexts
Traceback (most recent call last):
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/connection.py”, line 160, in _new_conn
(self._dns_host, self.port), self.timeout, **extra_kw
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/util/connection.py”, line 84, in create_connection
raise err
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/util/connection.py”, line 74, in create_connection
sock.connect(sa)
OSError: [Errno 51] Network is unreachable

During handling of the above exception, another excepv tion occurred:

Traceback (most recent call last):
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/connectionpool.py”, line 677, in urlopen
chunked=chunked,
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/connectionpool.py”, line 392, in _make_request
conn.request(method, url, **httplib_request_kw)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/http/client.py”, line 1272, in request
self._send_request(method, url, body, headers, encode_chunked)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/http/client.py”, line 1318, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/http/client.py”, line 1267, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/http/client.py”, line 1038, in _send_output
self.send(msg)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/http/client.py”, line 976, in send
self.connect()
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/connection.py”, line 187, in connect
conn = self._new_conn()
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/connection.py”, line 172, in _new_conn
self, “Failed to establish a new connection: %s” % e
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7febac8cdc88>: Failed to establish a new connection: [Errno 51] Network is unreachable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/requests/adapters.py”, line 449, in send
timeout=timeout
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/connectionpool.py”, line 727, in urlopen
method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/util/retry.py”, line 439, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host=‘qiita.ucsd.edu’, port=7329): Max retries exceeded with url: /HGETALL/state:contexts (Caused by NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x7febac8cdc88>: Failed to establish a new connection: [Errno 51] Network is unreachable’,))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/Users/rui/anaconda3/envs/qiime2-2020.8/bin/redbiom”, line 8, in
sys.exit(cli())
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/click/core.py”, line 829, in call
return self.main(*args, **kwargs)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/click/core.py”, line 782, in main
rv = self.invoke(ctx)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/click/core.py”, line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/click/core.py”, line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/click/core.py”, line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/click/core.py”, line 610, in invoke
return callback(*args, **kwargs)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/redbiom/commands/summarize.py”, line 16, in summarize_caches
contexts = redbiom.summarize.contexts()
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/redbiom/summarize.py”, line 29, in contexts
contexts = get(‘state’, ‘HGETALL’, ‘contexts’)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/redbiom/_requests.py”, line 90, in f
return _parse_validate_request(s.get(url), cmd)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/requests/sessions.py”, line 543, in get
return self.request(‘GET’, url, **kwargs)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/requests/sessions.py”, line 530, in request
resp = self.send(prep, **send_kwargs)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/requests/sessions.py”, line 643, in send
r = adapter.send(request, **kwargs)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/requests/adapters.py”, line 516, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host=‘qiita.ucsd.edu’, port=7329): Max retries exceeded with url: /HGETALL/state:contexts (Caused by NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x7febac8cdc88>: Failed to establish a new connection: [Errno 51] Network is unreachable’,))

Network is unreachable using https proxy (python)

David Rager's profile photo

David Rager

unread,
May 9, 2014, 12:26:50 AM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

I am hitting an error here when trying to debug some other stuff - I am on an environment that requires a https proxy:

This is the URL tripping the error:

https://www.google.com/apis/ads/publisher/v201403/InventoryService?wsdl

Here is how I initialize the dfp Client and Oath client:

oauth2_client = oauth2.GoogleRefreshTokenClient(CLIENT_ID, CLIENT_SECRET, REFRESH_TOKEN, https_proxy=https_proxy)

dfp_client = dfp.DfpClient(oauth2_client, APPLICATION_NAME, network_code = NETWORK_CODE, https_proxy=https_proxy)

report_downloader = dfp_client.GetDataDownloader(version='v201403')

The error is throw from here (using googleads for python) - I'm not clear the proxy is being used by urllib2 but don't want to try any rewiring without specific direction:

Traceback (most recent call last):
File "/home/drager/etl/Bicep2/web2py/gluon/restricted.py", line 220, in restricted
exec ccode in environment
File "/home/drager/etl/Bicep2/web2py/applications/BICEP2/controllers/default.py", line 389, in <module>
File "/home/drager/etl/Bicep2/web2py/gluon/globals.py", line 385, in <lambda>
self._caller = lambda f: f()
File "/home/drager/etl/Bicep2/web2py/applications/BICEP2/controllers/default.py", line 17, in testAdUnits2
return dict(m=dfpPullAdUnits())
File "/home/drager/etl/Bicep2/web2py/applications/BICEP2/models/dfp.py", line 28, in dfpPullAdUnits
# function is pinned to a job
File "/home/drager/etl/Bicep2/web2py/site-packages/googleads/dfp.py", line 157, in GetService
self._SOAP_SERVICE_FORMAT % (server, version, service_name))
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/client.py", line 115, in __init__
self.wsdl = reader.open(url)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/reader.py", line 150, in open
d = self.fn(url, self.options)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/wsdl.py", line 136, in __init__
d = reader.open(url)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/reader.py", line 74, in open
d = self.download(url)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/reader.py", line 92, in download
fp = self.options.transport.open(Request(url))
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/transport/https.py", line 62, in open
return HttpTransport.open(self, request)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/transport/http.py", line 67, in open
return self.u2open(u2request)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/transport/http.py", line 132, in u2open
return url.open(u2request, timeout=tm)
File "/usr/local/lib/python2.7/urllib2.py", line 404, in open
response= self._open(req, data)
File "/usr/local/lib/python2.7/urllib2.py", line 422, in _open
'_open', req)
File "/usr/local/lib/python2.7/urllib2.py", line 382, in _call_chain
result = func(*args)
File "/usr/local/lib/python2.7/urllib2.py", line 1222, in https_open
return self.do_open(httplib.HTTPSConnection, req)
File "/usr/local/lib/python2.7/urllib2.py", line 1184, in do_open
raise URLError(err)
URLError: <urlopen error [Errno 101] Network is unreachable>
David Rager's profile photo

David Rager

unread,
May 9, 2014, 12:54:48 AM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

My ad unit service call:

ad_unit_service = dfp_client.GetService('InventoryService',  'v201403', 'https://www.google.com')
David Rager's profile photo

David Rager

unread,
May 9, 2014, 8:29:20 PM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

This is working fine:
Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 9, 2014, 9:22:15 PM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi David,

Are you passing in an https proxy in this case? (setup with a ca_cert etc.)?

We're currently looking into what's the best way to implement this, as passing in a server setup with actual https seems like it's breaking the SSL handshake, you'd be verifying once at your proxy and then again at the end point server.

That said, your 404 might be because the expected URL is:

https://www.google.com/apis/ads/publisher/v201403/InventoryService?wsdl

it seems you're missing the ?wsdl at the end.

Best,

Nicholas Chen, DFP API Team

David Rager's profile photo

David Rager

unread,
May 9, 2014, 11:40:46 PM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi Nicholas - ty for jumping in.

I pass in the https_proxy in the two following calls:

oauth2.GoogleRefreshTokenClient(CLIENT_ID, CLIENT_SECRET, REFRESH_TOKEN, https_proxy=https_proxy)

and 

dfp.DfpClient(oauth2_client, APPLICATION_NAME, network_code = NETWORK_CODE, https_proxy=https_proxy)

https_proxy is what our IT group sent over.  It is also available as a python environmental variable.  They do PCI compliance and support a large number of installations so imagine it is set up correctly.  When using urllib2 directly I don't have an issue (assume it is using the environment var correctly). 

I found this on suds:

http://stackoverflow.com/questions/12414600/suds-ignoring-proxy-setting

I tried to rewire the transport but didn't have luck.  

I'm not clear why the debug wouldn't have the ?wsdl

The URL I am printing (with the ?wsdl) is being printed from the dfp Client __init__ function - the one without is printed by the python logging debug

David Rager's profile photo

David Rager

unread,
May 12, 2014, 7:54:13 PM5/12/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Just to clarify - I use the same code on a different network without the proxy and it all goes pretty smoothly.  https_proxy = None for that environment. 



On Friday, May 9, 2014 11:22:15 AM UTC-6, Nicholas Chen (DFP API Team) wrote:

Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 13, 2014, 2:08:45 AM5/13/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi David,

We're actually not using the pure suds implementation (so that might not be 100% relevant), we're using a fork of suds-jurko.

That said, I trust your proxy is setup properly, what's unclear - and this is a broader implementation type question that we're looking into. In any case where you've set up an https proxy in the middle, then I believe you're breaking the SSL handshake between yourself and DFP. From testing, it seems that passing in an http:// proxy to the https constructor (yes I realize this is counter-intuitive), then the traffic should get forwarded along without ever breaking that handshake. We're looking into whether or not this is the best thing to do now.

Best,

Nicholas Chen, DFP API Team

David Rager's profile photo

David Rager

unread,
May 14, 2014, 2:23:59 AM5/14/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Is that something I can try on my end?  Which constructor in particular should I try modifying, if so? 

Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 14, 2014, 6:49:50 PM5/14/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Yes, the same way you're passing in an https server as a proxy, you can pass in an http server to the https_proxy argument.

You can do this by manually instantiating your dfp_client OR by having your googleads.yaml file contain an 'https_proxy' arg that maps to an http server.

Best,

Nicholas Chen, DFP API Team

David Rager's profile photo

David Rager

unread,
May 15, 2014, 1:11:07 AM5/15/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]


Nicholas - I may not be following you.  I tried this:  

      proxy = {}

proxy['http'] = 'http://proxyserver:1234'

proxy['https'] = 'http://proxyserver:1234'

      client = suds.client.Client(self._SOAP_SERVICE_FORMAT % (server, version, service_name),proxy=proxy)

That still returned auth errors and <urlopen error Tunnel connection failed: 404 Not Found>

Were you indicating a different method of wiring up an http server?

David Rager's profile photo

David Rager

unread,
May 15, 2014, 2:54:43 AM5/15/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

I believe I had luck by removing the https_proxy from the GoogleRefreshTokenClient, including it in the client call and just sending in the proxy['http'] to the suds.client.Client constructor.

Still need to test some more tomorrow - let me know if that sounds close to what you were indicating.  

Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 15, 2014, 6:31:46 PM5/15/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi David,

That's not quite what I was thinking (removing it from the GoogleRefreshTokenClient), but the second part is what I was after, passing the proxy to suds - I think you'd get the same effect if you set the address in your googleads.yaml (it should flow down through the dfp_client constructor). For whatever reason, it seems like the refresh isn't happening when your proxy is being included on the request for OAuth (and OAuth alone).

Best,

Nicholas Chen, DFP API Team

David Rager's profile photo

David Rager

unread,
May 15, 2014, 8:41:29 PM5/15/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Thank you for the help and the tip on googleads.yaml - appreciate your time.  

David Rager's profile photo

David Rager

unread,
May 16, 2014, 1:07:40 AM5/16/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Flipped to the yaml with no better luck.  My hack doesn't appear to be working ATM either.  

Do you have any suggestions on how to debug this with my IT folks?

Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 16, 2014, 7:23:55 PM5/16/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi David,

To be clear, my suggestion was to include testing an http served proxy (passed in under the guise of an https proxy) to at least allow you to pass the requests through a proxy. I had also tested this with a squid proxy / ssl bump enabled for an https server, but I'm not sure how your IT team would set that up on their end:

http://wiki.squid-cache.org/Features/SslBump

But this is effectively man-in-the-middling the request and isn't necessarily better than passing in an http intermediate proxy server.

Best,

Nicholas Chen, DFP API Team

Hi,

After investigating a user complaint, we've discovered that the socket connect call -- "int connect(int s, const struct sockaddr *name, int namelen)" -- fails in our NePacketTunnelProvider in iOS 10.3.1 while on the T-Mobile network. We are using GCDAsyncUdpSocket for some calls in our VPN extension which makes a connect call (https://github.com/robbiehanson/CocoaAsyncSocket/blob/master/Source/GCD/GCDAsyncUdpSocket.m#L3323). The error is: Error Domain=NSPOSIXErrorDomain Code=51 "Network is unreachable". However, if the VPN is off, I can use the internet as expected through the Tmobile network, so this error seems suspicious.

I don't see this connect failure on other cellular networks (I've verified success with AT&T and Project Fi) or on Wi-Fi. Before we upgraded our test phones to 10.3.1 to try to repro a user complaint, we didn't see this error on the Tmobile network either. So it seems to be new in 10.3.1 (perhaps not 10.3.1 exactly but between 10.2 and 10.3.1 because the tests phones were on 10.1.X and 10.2.X before upgrading). It's not an issue with the iPhone hardware because the same phone will succeed with a Project Fi sim card but fail with the T-mobile sim card. Unfortunately this issues persists on the 10.3.2 beta.

I've verified that the cellular connection is good without the VPN by surfing the web and downloading URLS from the app.

I've verified that the VPN can download an URL via NSURLSessionDataTask even though the connect call error claims the network is unreachable.

I've verified that connect() calls don't fail in the app even though the VPN is on and they fail in the VPN, so it seems to be specific to NEPacketTunnelProvider.

Is this a known issue? Is there any other troubleshooting that we should do or any suggestions on how we might fix this?

Thanks!

Can’t connect from internet, get error 51

Hello,

I  try to use NoMachine free to connect to my machine from the internet. It works pretty well on local network, even when I connect through the public IP/port combo. However it doesn’t work as soon as I am outside of the local network, on the internet: I get error 51.

My machine is on Ubuntu 20.04, ethernet with CPL connection to an ISP router with UPNP enabled. I can see the rule generated to forward public 23868 to local machine 4000.

I have also manually opened 23868 on the router, but it doesn’t change anything. I have tried different things found on this page https://knowledgebase.nomachine.com/AR11L00827 but nothing works.

Please could you help me ?

Regards.

server: Ubuntu 20.04.2, Gnome 3.36.8, NoMachine free 7.6.2

client: iPad air 4, iPadOS 14.6, don’t know where to find version number of NoMachine client

router: bbox Fast5330b-r1, UPNP enabled, connection to machine over CPL

Error 51 network is unreachable - opinion you

Can’t connect from internet, get error 51

Hello,

I  try to use NoMachine free to connect to my machine from the internet. It works pretty well on local network, even when I connect through the public IP/port combo. However it doesn’t work as soon as I am outside of the local network, on the internet: I get error 51.

My machine is on Ubuntu 20.04, ethernet with CPL connection to an ISP router with UPNP enabled. I can see the rule generated to forward public 23868 to local machine 4000.

I have also manually opened 23868 on the router, but it doesn’t change anything. I have tried different things found on this page https://knowledgebase.nomachine.com/AR11L00827 but nothing works.

Please could you help me ?

Regards.

server: Ubuntu 20.04.2, Gnome 3.36.8, NoMachine free 7.6.2

client: iPad air 4, iPadOS 14.6, don’t know where to find version number of NoMachine client

router: bbox Fast5330b-r1, UPNP enabled, connection to machine over CPL

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

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

MUDEC_00001

Mudfish Launcher (mudrun) MUST be run as administrator

This error could happen if you're not running Mudfish Launcher as Administrator.

MUDEC_00002

Failed to connect to the master server.

This error points that it failed to connect to the mudfish master server for various operations.

If this error happens, you need to 'Status -> Process' menu to see "Core" log section. At that menu, please check there's an error or warning message because there's some messages to show the fundamental reasons.

MUDEC_00003

No TAP-Win32 Driver found.

TAP-Win32 adapter v9 network device is developed by OpenVPN Technologies, Inc and shipped with a part of Mudfish Cloud VPN.

My device isn't installed

Sometimes TAP-Win32 adapter v9 isn't properly installed even if the mudfish package try to install it automatically. To check whether it's installed or not

  1. Right click on the little computer screen next to your clock and click "Open Network and Sharing Center”
  2. then go to "Change Adapter Settings".
  3. Check there is a device called TAP-Windows-Adapter-V9.

If not, then you can try the following steps.

Workaround #1

  • Moves into the mudfish installation directory (normally ). At there you can find file.
  • Runs it as Administrator.
  • Install mudfish package again.

Workaround #2

You can install it manually by downloading tap-windows at https://openvpn.net/index.php/open-source/downloads.html link. Or you can try to install TAP-Win32 Driver as follows:

Workaround #3

  • Please check file too because it includes most detailed reason why your windows rejects the installation of TAP-Win32 adapter.

MUDEC_00012

Mudfish Launcher is already running.

This error means that on your system Mudfish Launcher is already running. Please check the system tray whether there is Mudfish Launcher icon. Or you can try to find mudrun.exe process with Task Manager.

MUDEC_00015

Failed to receive information from the master server for MR record:

This error means that Mudfish program failed to fetch mudfish node information from Mudfish master server. Depending , its meaning could be different:

  • ODR_ETIMEDOUT

    This error means that it failed to receive a data from master server within 5 seconds.

    It could be caused by

    • Some network firewall blocked a connection to Mudfish master server

    • Or a connection between your ISP and master server isn't stable.

    • Or Mudfish master server is busy.

You should restart Mudfish program again to fix this problem. If you think this issue is caused by blocking of network firewall, you can try to see Firewall Issues - Mudfish Master Server.

MUDEC_00016

Failed to receive information from the master server for MR record:

This issue is same error with MUDEC_00015. Please check MUDEC_00015 for details.

MUDEC_00018

failed to receive information from the master server:

This error means it failed to get the response from the mudfish master server for authentication. and <err_string> represent details about why this issue happens.

You can check Firewall Issues - Mudfish Master Server section for workarounds.

MUDEC_00022

CreateProcess failed with error :

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_00026

Wrong syntax on .conf file

This error means there's wrong syntax on file which is the configuration file for Mudfish Launcher. To solve this issue, please delete file which found at the mudfish installation directory and restart the mudfish.

MUDEC_00031

TOL_connect(, ) failed:

This error message happens if you enabled FastConnect mode. By unknown reason, it means it failed to connect and via mudfish node you'd picked.

If is 8081, it means that it failed to access SOCKS proxy. So as workaround,

  1. You can try to disable FastConnect mode

  2. Or you can try to change mudfish node you'd picked to another.

If is 8085, it means that it failed to access the TUNNEL proxy internally. shows details why it failed:

  • 64 Host is down

    This error means that there's no routing path to in mudfish core. Normally this issue means there's a problem to communicate with mudfish nodes you picked.

    Please try to change a mudfish node from one to another. If it still shows these error, please send us Problem Report.

MUDEC_00043

Failed to write the routing socket message for /// ()

This error means it failed to write (insert or delete) the routing table entry in Mudfish core process due to reason. Most common error messages are as follows:

  • No such process

    This means it could not delete the routing table entry because there's no matching entry.

    This is normally not harmful so you can ignore.

  • Network is unreachable (51)

    This error means that there's a routing table problem to reach to the mudfish node you'd picked.

    Please check the mudfish core process log at 'Status -> Process' menu to see the full errors. And please check there's another error before this error too.

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.

To see workarounds, please refer MUDEC_00045 because it's caused by same reason.

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 Windows 10, sometimes this issue is caused by Windows because it doesn't actively try to lease private IP address from TAP-Win32 adapter v9 network device.

    • Please open 'Task Manager'.

    • Or please try to keep "Change Adapter Settings" window open as follows:

      1. Right click on the little computer screen next to your clock at system tray.

      2. Click "Open Network and Sharing Center"

      3. Then click "Change Adapter Settings".

      4. Done! Just keep the window open.

  • If you're using v4.3.13 or above for Windows, you can try to use 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 Files\Mudfish Cloud VPN\mudrun.exe"

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

      "C:\Program Files\Mudfish Cloud VPN\mudrun.exe" -I

    • If this option is applied properly you can find a log as follow from Mudfish Core process which found at "Status → Process" menu::

      [INFO] Setting IP address (ip) with IP Helper.

  • 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.

    • If IPv6 is enabled for TAP-Win32 adapter v9 network device, please disable it completely. Sometimes this solves the problem.

MUDEC_00049

no entry for SID

This issue could happen by multiple reasons as follows:

  1. If you just bought the mudfish credit, you need to restart the mudfish program completely. Sometimes you can encounter this issue when you try to connect a mudfish node without restarting the problem.

  2. If your data plan is "Subscription", you need to equip the Subscription voucher. Please check it at http://mudfish.net/admin/user/dataplan/modify link.

  3. If a negative credit or no credit in your current account.

  4. If your equipped item is configured with invaild / dead mudfish node.

  5. If the mudfish node information doesn't be served by master server because of temporarily matter or permanently shutdown of the service.

  6. If you limits the list of mudfish nodes at 'Setup -> Nodes' menu, sometimes this issue could happen. To solve this issue, you can clear the list limitation.

MUDEC_00051

Failed to set the default route.

This error means that it failed to set the default route internally for mudfish core program. Normally it's caused that it failed to fetch the mudfish node information or not permitted by various reason. For most of cases, it's related with mudfish credit.

  • Please check your account has a mudfish credit.

  • If your data plan is Subscription based, please make sure that at least one paid item is equipped.

MUDEC_00059

ODR_write() error to : <err_num>

This error means that it failed to send the data via mudfish node whose public IP is because it encountered . The details about error messages are as follows:

  • ODR_ENOTCONN

    It failed to connect to the mudfish node due to failure of TCP handshake.

  • ODR_EAGAIN

    This error means that the connection isn't established yet but it tried to send the data to the mudfish node.

    If this issue is always happening, please try to change a mudfish node to another one.

If this error happens, please try to change the mudfish node or Connection Protocols.

MUDEC_00062

ODR_read() for hdr error from :

This error means that a connection between your desktop and mudfish node you used is aborted by reason. The details about error messages are as follows:

  • ODR_ECONNABORTED

    The virtual circuit was terminated due to a time-out or other failure. The application should close the socket as it is no longer usable.

  • ODR_ECONNRESET

    The virtual circuit was terminated by the reset packet from the mudfish node (peer). It means the connection between mudfish node and your desktop is corrupted or there's a problem at mudfish node side. Normally this issue isn't from your side. It could be a problem of the mudfish node you'd picked.

    Please try to use other mudfish nodes.

  • ODR_ETIMEDOUT

    The connection has been dropped, because of a network failure or because the system on the other end went down without notice. Normally this error means that mudfish node doesn't send any packets to you anymore.

MUDEC_00064

ODR_read() for payload error from : "

Please check MUDEC_00062 error link for details because it's from the same reason.

MUDEC_00066

ODR_recvfrom() error from :

This error means that it failed to receive the data from . This IP points the public IP of mudfish node you used. You need to check the error number and message for details:

  • 10090 ODR_EMSGSIZE

    This points that the message was too large to fit into the buffer pointed to by the mudfish and was truncated. This error isn't a common because the received data is over MCLBYTES (normally it's around 2 KB).

    If you stil encounter this issue, please consider to change Connection Protocols to TCP-based one.

MUDEC_00079

Failed to connect the master server ::

This error means that you can't connect to the master server using :. Are you under network firewall? If then it could be possible if the firewall blocks an access to mudfish sites.

For this case, please check Mudfish Master Server link for details how to avoid.

MUDEC_00080

TOL_sendto(2) error to <device_name> <private_ip> for heartbeat. ()

Why?

This error message means it failed to send a heartbeat packet to the target mudfish node .

However if its error level is "[INFO]" not "[ERROR]", you can ignore this error message because it doesn't affect your connection

Solution

  • Please try to change a mudfish node to others

  • Or please try to change "Connection Protocol" found under "Setup → Program" menu.

  • Or please contact to the mudfish forums.

MUDEC_00086

ReadFile() error (handle <handle_no>):

This error is related with TAP-Win32 adapter v9 network adapter when it failed to do 'read' operation. For details, and shows the detailed message about why:

  • 2 The system cannot find the file specified.

    This message means that it failed to find a file associated with TAP-Win32 adapter v9 adapter. This error could happen when some other processes aborted the network adapter forcibly.

MUDEC_00124

CreateIpForwardEntry() failed:

This error means that Mudfish core process failed to insert the routing path into your host OS. and points an exact reason of this failure. Known error messages are as follows:

  • One or more arguments are not correct.

    This error means it passed the invalid arguments for calling CreateIpForwardEntry() function. If you encounter this issue, please send Problem Report for details.

MUDEC_00126

ODR_CreateIpForwardEntry failed: IP // (ifindex metric )

This error means that it failed to create the forwarning entry (routing table) for Windows. Please check 'Status → Process' menu for previous errors first. Normally you can see MUDEC_00124 error before this error which shows a reason error message.

MUDEC_00129

ODR_CreateIpForwardEntry failed: IP // (ifindex <interface_index> metric <metric_value>)

This error means that Mudfish core process failed to insert the routing path (, and ) into your host OS.

MUDEC_00137 (router)

ODR_writev() error:

If points ODR_EIO, please ignore this error message because it's not harmful.

MUDEC_00139

ODR_read() error:

This error means that it failed to read a data from tap(4) driver (in Windows, it's called as TAP-Win32 adapter v9). and points details:

  • 10011 ODR_ENOENT

    Please check MUDEC_00086 error section and see '2 The system cannot find the file specified.' entry for details.

MUDEC_00145

udp_relay: TOL_sendto(2) failed to <private_ip>: <error_num> <error_msg>

This error could happen if you're using FastConnect mode. It indicates that it failed to send packets to mudfish node whose private IP is <private_ip> due to <error_msg>.

  • No buffer space available

    It means too many connections are made from your desktop to Mudfish so no more resources are available to keep the connections.

  • Host is down

    It means the connection between your desktop and mudfish node you'd picked isn't established yet.

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_00180

TCP_socket(2) failed: <err_string>

This error could happen if you enabled FastConnect mode. Depending on number, its reason could be different:

  • 55 No buffer space available

    This message means that Mudfish program could not create a TCP socket anymore due to out of resources allocated for program. This message caused by that your desktop created too many connections to the internet.

    Please check the following things:

    • If Full VPN mode is enabled, please turn off if it's not required.

    • Or please terminate any other programs cause the network traffics or connections.

MUDEC_00186

Wrong TCP format hdr:

This error means that your connection is something wrong to communicate with mudfish node you'd picked. Or your connection is monitored and filtered by network firewalls.

You can try to use other Connection Protocols or change a mudfish node.

MUDEC_00192

Failed to open '/dev/tap7': <err_string>

Depending on code, the fundamental reason could be different. Please check the following lists.

  • Please use latest Mudfish version available at https://mudfish.net/download link. No longer tuntap driver is used for Mac OS X.

  • Sometimes this issue is caused by that already mudfish process is running. Please check 'mudfish' process is running and kill it.

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.

MUDEC_00238

Packet loss rate to

This message means that you're using for mudfish configuration but mudfish found that your connection between your desktop and mudfish node you picked is unstable. points the name of mudfish node you selected. points the packet loss rate. To solve this issue, you should:

  • If you're familiar with WinMTR, please check How to use WinMTR link and test to the public IP of mudfish node you picked. The public IP of mudfish node is found at http://mudfish.net/server/status link.

    It'll show where this packet loss is from.

  • Please check your ISP first. Sometimes this issue could be caused by your ISP side.

  • If your ISP works fine, please try to change mudfish node to another. Sometimes this could be helpful to solve this issue.

MUDEC_00254

authc_read() failed:

This issue points that it failed the configuration information from the mudfish master server. So it means that there's a problem to communicate with the master server.

You need to check Firewall Issues - Mudfish Master Server section for workarounds.

MUDEC_00258

Failed to fetch the configuration.

This error is same one with MUDEC_00254.

MUDEC_00262

ODR_sendto() error to <ip_addr> Message too long. Check your path MTU. (curmtu buflen

This error means there is a MTU (Maximem Transmission Unit) error from your desktop to mudfish node you're using whose IP address is <ip_addr>.

Workaround #1

This workaround is recommended rather than workaround #2 not to lose any performance. To fix this problem, you should modify MTU value of TAP-Win32 adapter v9 network adapter and follow these steps:

  1. Open Network Connections by clicking the Start button, and then clicking Control Panel. In the search box, type adapter, and then, under Network and Sharing Center, click View network connections.

  2. Right-click TAP-Win32 adapter v9 connection, and then click Properties. Administrator permission required If you're prompted for an administrator password or confirmation, type the password or provide confirmation.

  3. Click Configure button at Networking tab.

  4. At Advanced tab, you can find MTU property. So you can reduce its value (e.g. 1400, 1300 and etc) from 1500 (default value) until this message is gone.

Workaround #2

Sometimes this issue is solved by changing the connection protocol from UDP to TCP.

  1. Visits 'Setup → Program' menu.

  2. Changes to TCP based protocol / port.

MUDEC_00269

udp_relay: TOL_sendmsg(2) to : failed:

This error message is shown only if you turned on FastConnect mode. This shows that it failed to send a UDP packet to : through Mudfish. represents a detail reason as follows:

  • 55 No buffer space available

    This means no more buffer space on UDP socket used by UDP proxy of Mudfish. Normally it points that there's a problem to communicate with mudfish node.

    To solve this problem:

    • You can try to turn off FastConnect mode.
    • Or you can try to use other mudfish nodes.
    • Or you can try to change the connection protocol to another.

MUDEC_00279

arp:

This error means that something is wrong at Mudfish services. Please contact to us via Mudfish Forums to fix this.

MUDEC_00281

Failed to fetch the routing table.

This error means Mudfish failed to receive the routing table information from master server. Sometimes it could be failed due to network issue but if it keeps persistent, please try to follow below:

MUDEC_00282

Failed to receive heartbeat resp -1

This error means Mudfish failed to receive a heartbeat response from the master server. Sometimes it could be failed due to network issue but if it keeps persistent, it means one of followings:

  • Network Firewall could block your connection.

  • A connection between your ISP and mudfish master server isn't stable.

MUDEC_00285

CryptAcquireContext failed with error :

This issue could happen while Mudfish try to check the permission of creating the encryption key.

  • 0x80090024 The profile for the user is a temporary profile

    Please check MUDEC_00286 section for workarounds.

MUDEC_00286

MUDEC_00286: CryptAcquireContext, newkeyset failed with error:

This error could happen at very beginning while Mudfish Launcher is executed. It means it failed to initialize the random key generator using current your account. Normally this issue happens because the password for account isn't set. To solve this problem you can try to

  • Create an other user account for Windows OS then try with it.

  • Or set a password for current user's password.

MUDEC_00305

Failed to receive information from the master server for MR record:

This error means that it failed to fetch the information of mudfish nodes from mudfish master server.

points the reason about why this issue happens:

  • ODR_ETIMEDOUT

    This message means that receiving the data was timed out. So it means the master server didn't respond or there's other network error due to network firewall.

To solve this problem you can try to

  • Checks Firewall - Mudfish Master Server document if you feel the connection blocked by network firewall.

  • Use other mudfish nodes or restart the mudfish problem.

MUDEC_00306

Failed to receive information from the master server for MS record:

This issue is same error with MUDEC_00305. Please check MUDEC_0030t for details.

MUDEC_00309

Failed to write the routing socket message:

This error means that it failed to add the rouing table entry in the mudfish core. and indicate why it was failed. Here's detailed error messages:

  • 51 Network is unreachable

    This error means it's not possible to connect the mudfish node you'd picked. For this case, please try to change a mudfish node from one to another.

MUDEC_00314

Failed to get any OS level event for reconnecting.

This error means that Mudfish back-end virtual driver couldn't get any events from OS (Windows / Windows / Mac OS X) regarding to the connection. This issue could happens if your network firewall on desktop or other network blocks the connection between your desktop and mudfish node you'd picked.

To solve this problem you can try to do

  1. Try to use other mudfish nodes.

  2. Or change Connection Protocols to another.

MUDEC_00316

Failed to receive information. / /

This error message means that you failed to get the routing table information after authentication.

MUDEC_00319

Failed to authenticate using ID/PWD

This error means that it failed to authenticate using your current username and password.

However if your password works to visit the mudifish web site but doesn't work with Mudfish Launcher, please visit http://accounts.en.loxch.com and try to change your password to simple combination. Then try it again.

MUDEC_00320

Failed to fetch the static node information.

This error means that it failed to fetch the static node information from the mudfish master server. For most of cases this error could happen by one of the followings:

  • When the connection between your ISP and mudfish master server is unstable.

  • Or when something blocks the connection to the mudfish master server.

  • Or your OS system has a wrong winsock setup.

To solve this problem, please try the followings:

MUDEC_00330

Slowed down due to speed limitation.

This error is caused by that your data plan is Subscription. At Subscription it has a speed cap so your traffics could be dropped by mudfish program if its limitation is hit.

To solve this problem, you can try one of the following things:

  1. You can try to change your data plan to PPT (Pay Per Traffic).

  2. Or terminate the program making network activities to reduce the network traffic usage.

  3. Or you can upgrade your voucher type for Subscription data plan. For details, you can visit https://mudfish.net/admin/user/dataplan/modify link.

MUDEC_00333

Failed to fetch static node information.

This error means it failed to lease IP address to communicate with a node link. When this issue still happens, please visit 'Status → Process' menu to see the core logs. It'll show other error or warning messages which happened before this error.

MUDEC_00338

Failed to receive a data. (res / )

This error points that it failed to receive a data from the mudfish master server. It means that it tried to read but failed with .

When this issue still happens, please visit 'Status → Process' menu to see the core logs. It'll show other error or warning messages which happened before this error.

MUDEC_00350

Failed to connect to the mudfish master server.

This error means that it failed to connect to the master server of mudfish for authentication. Please check 'Status -> Process' menu to see the core logs. You can find other error or warning level messages before this code.

MUDEC_00351

Failed to recvfrom(2) the data from master server. Error

This error means it failed to connect to the master server of Mudfish for authentication.

MUDEC_00357

Your account isn't activated.

This error means that the mudfish authentication server blocks your connection because too many tries for ID/PWD authentication within 1 minutes.

Please check your browser or mudfish programs whether it does wrong or not. So please wait around 5 minutes and try to login again.

MUDEC_00405

VSS_open(:) failed:

This error means you failed to connect :. The reason depends on as follows:

  • 2 (SELECT_TIMEOUT)

    This means that the connection was timed out. For most of cases, this issue is caused by the network firewall.

  • 5 (GETADDRINFO_ERROR)

    This means that it failed to perform DNS resolving for the domain. Sometimes this issue could happen your DNS requests are inspected by network firewall.

MUDEC_00409

Failed to connect the RTT server.

This error means that it failed to connect to the master server of mudfish for RTT information. Please check 'Status -> Process' menu to see the core logs. It'll show more details about why.

MUDEC_00410

Failed to connect the master server.

This error means that it failed to connect to the master server of mudfish for authentication. Please check 'Status -> Process' menu to see the core logs. It'll show more details about why.

MUDEC_00414

Failed to connect due to .

This error points that mudflow (Mudfish Flow Controller) process failed to connect . Normally points the private IP address of mudfish node you picked. points the specific reason why it failed:

  • WSAEACCES

    This error means your Windows OS blocks the connection. For most of cases it's caused by AV (Anti Virus) program.

    Please try to add mudfish processes as follows to the exceptional list:

    • mudfish.exe
    • mudflow.exe
    • mudrun.exe

MUDEC_00415

Failed to connect (errno )

This error points that it failed to connect to set up the configuration for Advanced Node / MultiPath Node settings. Normally is the private IP and port of mudfish node you'd picked.

indicates the reason:

  • 10053 (WSAECONNABORTED)

    An established connection was aborted by the software in your host machine.

    Are you using AV (anti-virus) / firewall program? Please check that those are blocking a connection of mudfish first.

    This message indicates that the connection is aborted by the software you're using on your box.

  • 10065 (WSAEHOSTUNREACH)

    No route to host. A socket operation was attempted to an unreachable host.

If this issue happens, please try to change a mudfish node setting to another combination.

MUDEC_00416

Failed to connect to : (errno )

This error points that it failed to connect to set up the configuration for Advanced Node / MultiPath Node settings. Normally is the private IP and port of mudfish node you'd picked. This error is like MUDEC_00415 but this is happening on Linux or Mac OS X environments.

indicates the reason:

  • Mac OS X

    • 60 (ETIMEDOUT)

      Operation timed out. It tried to connect but failed within the timeout.

MUDEC_00421

No mudfish nodes picked for the advanced node for the item

This error points that it failed to pick a mudfish node which used for advanced mode or multipath mode. For most of cases, it's related with "Auto Select" option for mudfish node pick-up.

To solve this problem:

MUDEC_00424

RTT stddev values are over 15% of your RTT avg to the closest mudfish nodes. Please check your ISP whether there's an issue or network congestion.

This error indicates the RTT standard deviation is more than 15% of the mean value while performing RTT calculcation internally.

If you see this message, it means that the connections to mudfish nodes closest to your current location are unstable. The detailed calculation formula is:

  1. Picks 6 mudfish nodes closest to the current user among all mudfish nodes and periodically performs RTT calculation.

  2. If all six checked mudfish nodes show an RTT stddev (standard deviation) of more than 15% of the RTT avg (average), a warning message is displayed.

If this error persists, please check the following things:

  • Do you use wireless connection (WIFI) rather than the LAN cable to connect the internet? If you're using WIFI, RTT stddev could be affected by the strength of WIFI signals.

  • Check your ISP or check whether you have internal QoS or firewall settings.

MUDEC_00440

recv(2) error: read error

This error means that it failed to receive the data from the mudfish master server or nodes. The reason depends on :

  • 10060 WSAETIMEDOUT

    This message means that receiving the data was timed out. So it means the master server didn't respond or there's other network error due to network firewall or other reason.

MUDEC_00446

Give up to wait the snode backed for SID

This error means that the mudfish flow controller (mudflow.exe) can't find a mudfish node information you set. If you see this mesagee, you can check the following things:

  • Checks your mudfish credits. Sometimes this issue is caused by out of mudfish credits.

  • Or visit 'Setup -> Nodes' menu and clear your limitation for picking the mudfish nodes. Sometimes this issue is caused by mismatch of mudfish node information between the mudfish flow controller and the mudfish core.

  • Or if all other things are fine but this issue still happens, please check Mudfish Master Server link and consider to test with option.

MUDEC_00463

Failed to send to the routing information (localip errno )

This error points that it failed to send the routing table information to the mudfish node you'd picked for Advanced Node Mode. If this issue persists, you can try to change the node mode from Advanced Mode to Basic Mode or Multi-Path Mode.

indicates why this error happens:

  • 10054 (WSAECONNRESET: Connection reset by peer)

    An existing connection was forcibly closed by the mudfish node. Normally it means that there's a problem to connect.

MUDEC_00464

AddIPAddress() failed:

This error could happen if you're using option for mudfish launcher. Depending on , it could mean different reasons as follows:

  • 5010 (ERROR_OBJECT_ALREADY_EXISTS)

    This error code means there's already a exisiting object to TAP-Win32 network v9 adapter. So you can ignore if mudfish works fine.

MUDEC_00467

Failed to recvfrom(3) the flush information (received / expected / errno / sid )

This error means that it failed to receive the data from the mudfish node you're using. The reason depends on :

  • 10060 WSAETIMEDOUT

    This message means that receiving the data was timed out. So it means the master server didn't respond or there's other network error due to network firewall or other reason.

MUDEC_00470

Increasing no of fragmented packets.

If the issue is still happening, it means that current network device (NIC) is constantly receiving fragmented packets. You can ignore this error message if you don't have any problems to use mudfish. However the packet loss rate could be affected by fragmented packet.

It is recommended to resolve the issue as much as possible because it increases.

Usually, one of the followings can cause this issue:

  • MTU (Maximum Transmission Unit) of NIC network device has an unusually small value.

  • If MTU value used for communication with the mudfish nodes is larger than expected, this issue could happen.

Please check the following list to resolve this issue.

  1. Check MTU (Maximum Transmission Unit) of currently installed network devices. For ethernet its default value is 1500. If it's more smaller, you can reset to the default value.

  2. If you enter the mudfish UI 'Settings -> Program' menu, there is an MTU menu. Try setting this value to 1400 (the mudfish default) or 1300.

MUDEC_00477

Too big UDP packet to send.

This error means that your game client is trying to send a bigger UDP packet than what mudfish could handle.

Please visit 'Setup -> Program' menu and adjust your MTU with lowering the value. For example, you can try to test with the following values:

MUDEC_00496

WSAIoctl() failed: error retbytes

This error means the redirect record associated with the socket failed to fetch. indicates more details:

  • 10022 (WSAEINVAL)

    Normally this error means the mudfish kernel driver for windows filtering platform is conflict with other AV (anti-virus) or firewall programs.

    Please check that on your machine there's a program which could intercept your connection and do something. If there's one, you can try to uninstall it and test it again.

    As a workaround, you can try

    • Turn off WFP Item mode.

      This will disable WFP feature of mudfish and no longer you will encounter this issue.

    • If you still want to use WFP Item mode, you can send us the result of from Command Prompt to check which the kernel drivers are loaded.

MUDEC_00501

bind failed with error:

This error means that it failed to bind a socket with specific IP:port for listener. The explains why:

  • 10048 WSAEADDRINUSE

    Only one usage of each socket address (protocol/network address/port) is normally permitted.

    Please make sure that all mudfish processes are restarted properly. Normally this error points that a mudfish process is already running.

MUDEC_00514

StartService() failed:

In the case of this error, it means that the windows service for Mudfish WFP (Windows Filtering Platform) driver did not run properly. The detailed reason depends on the value of .

  • 0x7f (ERROR_PROC_NOT_FOUND)

    In this case, there can be two cases.

    1. This may occur if the mudwfp.sys driver is not installed properly. Please check if the mudfish package was installed properly and there were no errors during the installation process.

    2. Or, if the Windows version you are using is 7 or lower. For the WFP feature, it must be at least Windows 8 or higher to work properly.

MUDEC_00539

Checking RTT to mudfish nodes are failing. Are you under network firewall?

When mudfish is launched, the program measures RTT (Round Trip Time) between your desktop and mudfish nodes. This error indicates that the RTT measurement is failed or RTT is relatively high (above 1.5 secs).

Please check that you're under network firewall. And try to change 'RTT Checking Method' found at 'Setup -> Program' menu.

MUDEC_00546

NetworkExtension isn't ready yet

This error means that mudfish core process didn't get any responses from mudfish NetworkExtension module. Please check two things first:

  • Check that VPN Configuration for mudfish is installed properly.

  • System Extension module for mudfish is installed properly. You should explicitly enable the systemextension module for mudfish.

To solve this issue, please try to uninstall mudfish completely and try to reinstall mudfish from the scratch. You can check the following links:

MUDEC_00555

Failed to sendto the ping information. (errno )

This error means you're using "Advanced Node mode" for the game item settings but failed to send a ping probe to the mudfish nodes you're using. indicates details why:

  • 10054 (WSAECONNRESET)

    Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close. This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress.

MUDEC_00556

Failed to connect mudfish short_path server.

This error indicates that mudfish program can't access to domain using TCP 10012 to get the recommended routing path. Please check 'Status -> Process' menu to see the detailed error reason.

In the log file, other error messages will exist.

MUDEC_00567

vhttp_rxhdr error.

This error indicates that mudfish program failed to parse HTTP response header got from the server specified. Please check 'Status -> Process' menu to see the detailed error reason.

In the log file, other error messages will exist.

MUDEC_00572

VHTTP_rxbody error.

This error indicates that mudfish program failed to send HTTP POST request to the server specified. Please check 'Status -> Process' menu to see the detailed error reason.

In the log file, other error messages will exist.

MUDEC_00586

recv(2) error: read error

This error points that there's a problem to receive the data from mudfish master server or mudfish RTT server. indicates the detailed reason:

  • 10060 (WSAETIMEDOUT)

    Connection timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.

If this issue still happens, please check Mudfish Master Server link and consider to test with option.

MUDEC_00724

ODR_read() for hdr error from :

This error points that one of the brokers for Multi-Path support encountered an error. If you don't have a problem with your game connection, you can ignore this issue.

  • This is a public IP of mudfish node which Multi-Path broker used.

  • Please check MUDEC_00062 error link for details because it's from the same reason.

MUDEC_00729

ODR_read() for payload error from : "

Please check MUDEC_00062 error link for details because it's from the same reason.

MUDEC_00748

No DHCP enabled for TAP-Win32 adapter v9

In case of this error, it means that DHCP setting is not enabled for the TAP-Win32 adapter v9 device installed in the system when Mudfish is installed.

To resolve this issue, please do the following:

  • Go to Control Panel -> Network and Internet -> Change adapter options menu.

  • From there, open the properties window of the TAP-Win32 adapter v9 device.

  • Open the properties of the 'Network -> Internet Protocol Version 4 (TCP/IPv4)' item.

  • Then enable the "Obtain an IP address automatically" function there. Also enable "Obtain DNS server address automatically".

After doing this, restart the mudfish completely and the problem will be solved.

MUDEC_00800

Due to too much data used in this month, your speed cap is more limited.

If your data plan is Subscription, this issue could happen when the monthly maximum usage of the subscription voucher is exceeded.

For detailed usage limits, please refer to Data Plans link.

QIIME 2 Forum

(qiime2-2020.8) Rui-Mac:~ rui$ redbiom summarize contexts
Traceback (most recent call last):
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/connection.py”, line 160, in _new_conn
(self._dns_host, self.port), self.timeout, **extra_kw
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/util/connection.py”, line 84, in create_connection
raise err
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/util/connection.py”, line 74, in create_connection
sock.connect(sa)
OSError: [Errno 51] Network is unreachable

During handling of the above exception, another excepv tion occurred:

Traceback (most recent call last):
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/connectionpool.py”, line 677, in urlopen
chunked=chunked,
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/connectionpool.py”, line 392, in _make_request
conn.request(method, url, **httplib_request_kw)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/http/client.py”, line 1272, in request
self._send_request(method, url, body, headers, encode_chunked)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/http/client.py”, line 1318, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/http/client.py”, line 1267, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/http/client.py”, line 1038, in _send_output
self.send(msg)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/http/client.py”, line 976, in send
self.connect()
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/connection.py”, line 187, in connect
conn = self._new_conn()
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/connection.py”, line 172, in _new_conn
self, “Failed to establish a new connection: %s” % e
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7febac8cdc88>: Failed to establish a new connection: [Errno 51] Network is unreachable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/requests/adapters.py”, line 449, in send
timeout=timeout
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/connectionpool.py”, line 727, in urlopen
method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/urllib3/util/retry.py”, line 439, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host=‘qiita.ucsd.edu’, port=7329): Max retries exceeded with url: /HGETALL/state:contexts (Caused by NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x7febac8cdc88>: Failed to establish a new connection: [Errno 51] Network is unreachable’,))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/Users/rui/anaconda3/envs/qiime2-2020.8/bin/redbiom”, line 8, in
sys.exit(cli())
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/click/core.py”, line 829, in call
return self.main(*args, **kwargs)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/click/core.py”, line 782, in main
rv = self.invoke(ctx)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/click/core.py”, line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/click/core.py”, line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/click/core.py”, line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/click/core.py”, line 610, in invoke
return callback(*args, **kwargs)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/redbiom/commands/summarize.py”, line 16, in summarize_caches
contexts = redbiom.summarize.contexts()
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/redbiom/summarize.py”, line 29, in contexts
contexts = get(‘state’, ‘HGETALL’, ‘contexts’)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/redbiom/_requests.py”, line 90, in f
return _parse_validate_request(s.get(url), cmd)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/requests/sessions.py”, line 543, in get
return self.request(‘GET’, url, **kwargs)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/requests/sessions.py”, line 530, in request
resp = self.send(prep, **send_kwargs)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/requests/sessions.py”, line 643, in send
r = adapter.send(request, **kwargs)
File “/Users/rui/anaconda3/envs/qiime2-2020.8/lib/python3.6/site-packages/requests/adapters.py”, line 516, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host=‘qiita.ucsd.edu’, port=7329): Max retries exceeded with url: /HGETALL/state:contexts (Caused by NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x7febac8cdc88>: Failed to establish a new connection: [Errno 51] Network is unreachable’,))

Network is unreachable using https proxy (python)

David Rager's profile photo

David Rager

unread,
May 9, 2014, 12:26:50 AM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

I am hitting an error here when trying to debug some other stuff - I am on an environment that requires a https proxy:

This is the URL tripping the error:

https://www.google.com/apis/ads/publisher/v201403/InventoryService?wsdl

Here is how I initialize the dfp Client and Oath client:

oauth2_client = oauth2.GoogleRefreshTokenClient(CLIENT_ID, CLIENT_SECRET, REFRESH_TOKEN, https_proxy=https_proxy)

dfp_client = dfp.DfpClient(oauth2_client, APPLICATION_NAME, network_code = NETWORK_CODE, https_proxy=https_proxy)

report_downloader = dfp_client.GetDataDownloader(version='v201403')

The error is throw from here (using googleads for python) - I'm not clear the proxy is being used by urllib2 but don't want to try any rewiring without specific direction:

Traceback (most recent call last):
File "/home/drager/etl/Bicep2/web2py/gluon/restricted.py", line 220, in restricted
exec ccode in environment
File "/home/drager/etl/Bicep2/web2py/applications/BICEP2/controllers/default.py", line 389, in <module>
File "/home/drager/etl/Bicep2/web2py/gluon/globals.py", line 385, in <lambda>
self._caller = lambda f: f()
File "/home/drager/etl/Bicep2/web2py/applications/BICEP2/controllers/default.py", line 17, in testAdUnits2
return dict(m=dfpPullAdUnits())
File "/home/drager/etl/Bicep2/web2py/applications/BICEP2/models/dfp.py", line 28, in dfpPullAdUnits
# function is pinned to a job
File "/home/drager/etl/Bicep2/web2py/site-packages/googleads/dfp.py", line 157, in GetService
self._SOAP_SERVICE_FORMAT % (server, version, service_name))
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/client.py", line 115, in __init__
self.wsdl = reader.open(url)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/reader.py", line 150, in open
d = self.fn(url, self.options)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/wsdl.py", line 136, in __init__
d = reader.open(url)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/reader.py", line 74, in open
d = self.download(url)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/reader.py", line 92, in download
fp = self.options.transport.open(Request(url))
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/transport/https.py", line 62, in open
return HttpTransport.open(self, request)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/transport/http.py", line 67, in open
return self.u2open(u2request)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/transport/http.py", line 132, in u2open
return url.open(u2request, timeout=tm)
File "/usr/local/lib/python2.7/urllib2.py", line 404, in open
response= self._open(req, data)
File "/usr/local/lib/python2.7/urllib2.py", line 422, in _open
'_open', req)
File "/usr/local/lib/python2.7/urllib2.py", line 382, in _call_chain
result = func(*args)
File "/usr/local/lib/python2.7/urllib2.py", line 1222, in https_open
return self.do_open(httplib.HTTPSConnection, req)
File "/usr/local/lib/python2.7/urllib2.py", line 1184, in do_open
raise URLError(err)
URLError: <urlopen error [Errno 101] Network is unreachable>
David Rager's profile photo

David Rager

unread,
May 9, 2014, 12:54:48 AM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

My ad unit service call:

ad_unit_service = dfp_client.GetService('InventoryService',  'v201403', 'https://www.google.com')
David Rager's profile photo

David Rager

unread,
May 9, 2014, 8:29:20 PM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

This is working fine:
Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 9, 2014, 9:22:15 PM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi David,

Are you passing in an https proxy in this case? (setup with a ca_cert etc.)?

We're currently looking into what's the best way to implement this, as passing in a server setup with actual https seems like it's breaking the SSL handshake, you'd be verifying once at your proxy and then again at the end point server.

That said, your 404 might be because the expected URL is:

https://www.google.com/apis/ads/publisher/v201403/InventoryService?wsdl

it seems you're missing the ?wsdl at the end.

Best,

Nicholas Chen, DFP API Team

David Rager's profile photo

David Rager

unread,
May 9, 2014, 11:40:46 PM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi Nicholas - ty for jumping in.

I pass in the https_proxy in the two following calls:

oauth2.GoogleRefreshTokenClient(CLIENT_ID, CLIENT_SECRET, REFRESH_TOKEN, https_proxy=https_proxy)

and 

dfp.DfpClient(oauth2_client, APPLICATION_NAME, network_code = NETWORK_CODE, https_proxy=https_proxy)

https_proxy is what our IT group sent over.  It is also available as a python environmental variable.  They do PCI compliance and support a large number of installations so imagine it is set up correctly.  When using urllib2 directly I don't have an issue (assume it is using the environment var correctly). 

I found this on suds:

http://stackoverflow.com/questions/12414600/suds-ignoring-proxy-setting

I tried to rewire the transport but didn't have luck.  

I'm not clear why the debug wouldn't have the ?wsdl

The URL I am printing (with the ?wsdl) is being printed from the dfp Client __init__ function - the one without is printed by the python logging debug

David Rager's profile photo

David Rager

unread,
May 12, 2014, 7:54:13 PM5/12/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Just to clarify - I use the same code on a different network without the proxy and it all goes pretty smoothly.  https_proxy = None for that environment. 



On Friday, May 9, 2014 11:22:15 AM UTC-6, Nicholas Chen (DFP API Team) wrote:

Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 13, 2014, 2:08:45 AM5/13/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi David,

We're actually not using the pure suds implementation (so that might not be 100% relevant), we're using a fork of suds-jurko.

That said, I trust your proxy is setup properly, what's unclear - and this is a broader implementation type question that we're looking into. In any case where you've set up an https proxy in the middle, then I believe you're breaking the SSL handshake between yourself and DFP. From testing, it seems that passing in an http:// proxy to the https constructor (yes I realize this is counter-intuitive), then the traffic should get forwarded along without ever breaking that handshake. We're looking into whether or not this is the best thing to do now.

Best,

Nicholas Chen, DFP API Team

David Rager's profile photo

David Rager

unread,
May 14, 2014, 2:23:59 AM5/14/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Is that something I can try on my end?  Which constructor in particular should I try modifying, if so? 

Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 14, 2014, 6:49:50 PM5/14/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Yes, the same way you're passing in an https server as a proxy, you can pass in an http server to the https_proxy argument.

You can do this by manually instantiating your dfp_client OR by having your googleads.yaml file contain an 'https_proxy' arg that maps to an http server.

Best,

Nicholas Chen, DFP API Team

David Rager's profile photo

David Rager

unread,
May 15, 2014, 1:11:07 AM5/15/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]


Nicholas - I may not be following you.  I tried this:  

      proxy = {}

proxy['http'] = 'http://proxyserver:1234'

proxy['https'] = 'http://proxyserver:1234'

      client = suds.client.Client(self._SOAP_SERVICE_FORMAT % (server, version, service_name),proxy=proxy)

That still returned auth errors and <urlopen error Tunnel connection failed: 404 Not Found>

Were you indicating a different method of wiring up an http server?

David Rager's profile photo

David Rager

unread,
May 15, 2014, 2:54:43 AM5/15/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

I believe I had luck by removing the https_proxy from the GoogleRefreshTokenClient, including it in the client call and just sending in the proxy['http'] to the suds.client.Client constructor.

Still need to test some more tomorrow - let me know if that sounds close to what you were indicating.  

Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 15, 2014, 6:31:46 PM5/15/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi David,

That's not quite what I was thinking (removing it from the GoogleRefreshTokenClient), but the second part is what I was after, passing the proxy to suds - I think you'd get the same effect if you set the address in your googleads.yaml (it should flow down through the dfp_client constructor). For whatever reason, it seems like the refresh isn't happening when your proxy is being included on the request for OAuth (and OAuth alone).

Best,

Nicholas Chen, DFP API Team

David Rager's profile photo

David Rager

unread,
May 15, 2014, 8:41:29 PM5/15/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Thank you for the help and the tip on googleads.yaml - appreciate your time.  

David Rager's profile photo

David Rager

unread,
May 16, 2014, 1:07:40 AM5/16/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Flipped to the yaml with no better luck.  My hack doesn't appear to be working ATM either.  

Do you have any suggestions on how to debug this with my IT folks?

Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 16, 2014, 7:23:55 PM5/16/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi David,

To be clear, my suggestion was to include testing an http served proxy (passed in under the guise of an https proxy) to at least allow you to pass the requests through a proxy. I had also tested this with a squid proxy / ssl bump enabled for an https server, but I'm not sure how your IT team would set that up on their end:

http://wiki.squid-cache.org/Features/SslBump

But this is effectively man-in-the-middling the request and isn't necessarily better than passing in an http intermediate proxy server.

Best,

Nicholas Chen, DFP API Team

In the case of network errors (e.g. a connection to a proxy server fails) Proxifier outputs error code numbers. These are the standard error codes. This section contains the codes of network errors and their description.

EPERM1Operation not permittedENOENT 2 No such file or directory ESRCH 3 No such process EINTR 4 Interrupted system call EIO 5 Input/output error ENXIO 6 Device not configured E2BIG 7 Argument list too long ENOEXEC 8 Exec format error EBADF 9 Bad file descriptor ECHILD 10 No child processes EDEADLK 11 Resource deadlock avoided ENOMEM 12 Cannot allocate memory EACCES 13 Permission denied EFAULT 14 Bad address ENOTBLK 15 Block device required EBUSY 16 Device / Resource busy EEXIST 17 File exists EXDEV 18 Cross-device link ENODEV 19 Operation not supported by device ENOTDIR 20 Not a directory EISDIR 21 Is a directory EINVAL 22 Invalid argument ENFILE 23 Too many open files in system EMFILE 24 Too many open files ENOTTY 25 Inappropriate ioctl for device ETXTBSY 26 Text file busy EFBIG 27 File too large ENOSPC 28 No space left on device ESPIPE 29 Illegal seek EROFS 30 Read-only file system EMLINK 31 Too many links EPIPE 32 Broken pipe EDOM 33 Numerical argument out of domain ERANGE 34 Result too large EAGAIN 35 Resource temporarily unavailable EWOULDBLOCK EAGAIN Operation would block EINPROGRESS 36 Operation now in progress EALREADY 37 Operation already in progress ENOTSOCK 38 Socket operation on non-socket EDESTADDRREQ 39 Destination address required EMSGSIZE 40 Message too long EPROTOTYPE 41 Protocol wrong type for socket ENOPROTOOPT 42 Protocol not available EPROTONOSUPPORT 43 Protocol not supported ESOCKTNOSUPPORT 44 Socket type not supported ENOTSUP 45 Operation not supported EPFNOSUPPORT 46 Protocol family not supported EAFNOSUPPORT 47 Address family not supported by protocol family EADDRINUSE 48 Address already in use EADDRNOTAVAIL 49 Can't assign requested address ENETDOWN 50 Network is down ENETUNREACH 51 Network is unreachable ENETRESET 52 Network dropped connection on reset ECONNABORTED 53 Software caused connection abort ECONNRESET 54 Connection reset by peer ENOBUFS 55 No buffer space available EISCONN 56 Socket is already connected ENOTCONN 57 Socket is not connected ESHUTDOWN 58 Can't send after socket shutdown ETOOMANYREFS 59 Too many references: can't splice ETIMEDOUT 60 Operation timed out ECONNREFUSED 61 Connection refused ELOOP 62 * Too many levels of symbolic links ENAMETOOLONG 63 File name too long EHOSTDOWN 64 Host is down EHOSTUNREACH 65 No route to host ENOTEMPTY 66 Directory not empty EPROCLIM 67 Too many processes EUSERS 68 Too many users EDQUOT 69 Disc quota exceeded ESTALE 70 Stale NFS file handle EREMOTE 71 Too many levels of remote in path EBADRPC 72 RPC struct is bad ERPCMISMATCH 73 RPC version wrong EPROGUNAVAIL 74 RPC prog. not avail EPROGMISMATCH 75 Program version wrong EPROCUNAVAIL 76 Bad procedure for program ENOLCK 77 No locks available ENOSYS 78 Function not implemented EFTYPE 79 Inappropriate file type or format EAUTH 80 Authentication error ENEEDAUTH 81 Need authenticator EPWROFF 82 Device power is off EDEVERR 83 Device error, e.g. paper out EOVERFLOW 84 Value too large to be stored in data type EBADEXEC 85 Bad executable EBADARCH 86 Bad CPU type in executable ESHLIBVERS 87 Shared library version mismatch EBADMACHO 88 Malformed Macho file ECANCELED 89 Operation canceled EIDRM 90 Identifier removed ENOMSG 91 No message of desired type EILSEQ 92 Illegal byte sequence ENOATTR 93 Attribute not found EBADMSG 94 Bad message EMULTIHOP 95 Reserved ENODATA 96 No message available on STREAM ENOLINK 97 Reserved ENOSR 98 No STREAM resources ENOSTR 99 Not a STREAM EPROTO 100 Protocol error ETIME 101 STREAM ioctl timeout EOPNOTSUPP 102 Operation not supported on socket ENOPOLICY 103 No such policy registered ELAST 103 Must be equal largest errno

9.10 mdnsresponder error 51 (Network is unreachable)

melloa said:

I agree the way to go with a server is to assign a SIP.

Click to expand...


FreeNAS does not support SIP.

Obviously that's not what you *meant*, but the point remains: Please do not make up new abbreviations especially where they overlap with a significant protocol within the networking scope of discussion.


melloa said:

For my own education, if the box is configured for DHCP, is that specified in /etc/rc.conf line synchronous_dhclient="YES" # Start dhclient directly on configured?

Click to expand...


No. It's specified in the GUI or in the console network configuration subsections. What happens under the sheets is "none of yer durn bizness" and is not meant for you to tinker with. FreeNAS is designed to be an appliance, managed through the middleware. This allows the developers to focus on providing functionality, and they can modify the base system, alter how it works, reimplement it entirely, etc., without it impacting the end user, who only knows that it is necessary to configure things via the GUI (which updates the database, which in turn drives the system configuration).

"synchronous_dhclient" is just a directive telling dhclient to operate synchronously... that is, to wait for a DHCP response before allowing the system to continue. Certain other things freak out if IP addresses aren't set (or sometimes if they change).

The actual network configuration is promulgated down into the host system through /etc/rc.conf.local, which provides some opportunity to see how values are retrieved from the configuration database.

 

Hi,

After investigating a user complaint, we've discovered that the socket connect call -- "int connect(int s, const struct sockaddr *name, int namelen)" -- fails in our NePacketTunnelProvider in iOS 10.3.1 while on the T-Mobile network. We are using GCDAsyncUdpSocket for some calls in our VPN extension which makes a connect call (https://github.com/robbiehanson/CocoaAsyncSocket/blob/master/Source/GCD/GCDAsyncUdpSocket.m#L3323). The error is: Error Domain=NSPOSIXErrorDomain Code=51 "Network is unreachable". However, if the VPN is off, I can use the internet as expected through the Tmobile network, so this error seems suspicious.

I don't see this connect failure on other cellular networks (I've verified success with AT&T and Project Fi) or on Wi-Fi. Before we upgraded our test phones to 10.3.1 to try to repro a user complaint, we didn't see this error on the Tmobile network either. So it seems to be new in 10.3.1 (perhaps not 10.3.1 exactly but between 10.2 and 10.3.1 because the tests phones were on 10.1.X and 10.2.X before upgrading). It's not an issue with the iPhone hardware because the same phone will succeed with a Project Fi sim card but fail with the T-mobile sim card. Unfortunately this issues persists on the 10.3.2 beta.

I've verified that the cellular connection is good without the VPN by surfing the web and downloading URLS from the app.

I've verified that the VPN can download an URL via NSURLSessionDataTask even though the connect call error claims the network is unreachable.

I've verified that connect() calls don't fail in the app even though the VPN is on and they fail in the VPN, so it seems to be specific to NEPacketTunnelProvider.

Is this a known issue? Is there any other troubleshooting that we should do or any suggestions on how we might fix this?

Thanks!

Network is unreachable using https proxy (python)

David Rager's profile photo

David Rager

unread,
May 9, 2014, 12:26:50 AM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

I am hitting an error here when trying to debug some other stuff - I am on an environment that requires a https proxy:

This is the URL tripping the error:

https://www.google.com/apis/ads/publisher/v201403/InventoryService?wsdl

Here is how I initialize the dfp Client and Oath client:

oauth2_client = oauth2.GoogleRefreshTokenClient(CLIENT_ID, CLIENT_SECRET, REFRESH_TOKEN, https_proxy=https_proxy)

dfp_client = dfp.DfpClient(oauth2_client, APPLICATION_NAME, network_code = NETWORK_CODE, https_proxy=https_proxy)

report_downloader = dfp_client.GetDataDownloader(version='v201403')

The error is throw from here (using googleads for python) - I'm not clear the proxy is being used by urllib2 but don't want to try any rewiring without specific direction:

Traceback (most recent call last):
File "/home/drager/etl/Bicep2/web2py/gluon/restricted.py", line 220, error 51 network is unreachable, in restricted
exec ccode in environment
File "/home/drager/etl/Bicep2/web2py/applications/BICEP2/controllers/default.py", line 389, in <module>
File "/home/drager/etl/Bicep2/web2py/gluon/globals.py", line 385, in <lambda>
self._caller = lambda f: f()
File "/home/drager/etl/Bicep2/web2py/applications/BICEP2/controllers/default.py", line 17, in testAdUnits2
return dict(m=dfpPullAdUnits())
File "/home/drager/etl/Bicep2/web2py/applications/BICEP2/models/dfp.py", line 28, in dfpPullAdUnits
# function is pinned to a job
File "/home/drager/etl/Bicep2/web2py/site-packages/googleads/dfp.py", line 157, in GetService
self._SOAP_SERVICE_FORMAT % (server, version, service_name))
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/client.py", line 115, in __init__
self.wsdl = reader.open(url)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/reader.py", line 150, in open
d = self.fn(url, self.options)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/wsdl.py", line 136, in __init__
d = reader.open(url)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/reader.py", line 74, in open
d = self.download(url)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/reader.py", line 92, in download
fp = self.options.transport.open(Request(url))
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/transport/https.py", line 62, in open
return HttpTransport.open(self, request)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/transport/http.py", line 67, in open
return self.u2open(u2request)
File "/home/drager/etl/Bicep2/web2py/site-packages/suds/transport/http.py", line 132, in u2open
return url.open(u2request, timeout=tm)
File "/usr/local/lib/python2.7/urllib2.py", line 404, in open
response= self._open(req, data)
File "/usr/local/lib/python2.7/urllib2.py", line 422, in _open
'_open', req)
File "/usr/local/lib/python2.7/urllib2.py", line 382, in _call_chain
result = func(*args)
File "/usr/local/lib/python2.7/urllib2.py", line error 51 network is unreachable, in https_open
return self.do_open(httplib.HTTPSConnection, req)
File "/usr/local/lib/python2.7/urllib2.py", line 1184, in do_open
raise URLError(err)
URLError: <urlopen error [Errno 101] Network is unreachable>
David Rager's profile photo

David Rager

unread,
May 9, 2014, 12:54:48 AM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

My ad unit service call:

ad_unit_service = dfp_client.GetService('InventoryService',  'v201403', 'https://www.google.com')
error 51 network is unreachable alt="David Rager's profile photo">

David Rager

unread,
May 9, 2014, 8:29:20 PM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

This is working fine:
Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 9, 2014, 9:22:15 PM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi David,

Are you passing in an https proxy in this case? (setup with a ca_cert etc.)?

We're currently looking into what's the best way to implement this, as passing in a server setup with actual https seems like it's breaking the SSL handshake, you'd be verifying once at your proxy and then again at the end point server.

That said, your 404 might be because the expected URL is:

https://www.google.com/apis/ads/publisher/v201403/InventoryService?wsdl

it seems you're missing the ?wsdl at the end.

Best,

Nicholas Chen, DFP API Team

David Rager's profile photo

David Immobilizer smartra error 9, 2014, 11:40:46 PM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi Nicholas - ty for jumping in.

I pass in the https_proxy in the two following calls:

oauth2.GoogleRefreshTokenClient(CLIENT_ID, CLIENT_SECRET, REFRESH_TOKEN, https_proxy=https_proxy)

and 

dfp.DfpClient(oauth2_client, APPLICATION_NAME, network_code = NETWORK_CODE, https_proxy=https_proxy)

https_proxy is what our IT group sent over.  It is also available as a python environmental variable.  They do PCI compliance and support a large number of installations so imagine it is set up correctly.  When using urllib2 directly I don't have an issue (assume it is using the environment var correctly). 

I found this on suds:

http://stackoverflow.com/questions/12414600/suds-ignoring-proxy-setting

I tried to rewire the transport but didn't have luck.  

I'm not clear why the debug wouldn't have the ?wsdl

The URL I am printing (with the ?wsdl) is being printed from the dfp Client __init__ function - the one without is printed by the python logging debug

David Rager's profile photo

David Rager

unread,
May 12, 2014, 7:54:13 PM5/12/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Just to clarify - I use the same code on a different network without the proxy and it all goes pretty smoothly.  https_proxy = None for that environment. 



On Friday, May 9, 2014 11:22:15 AM UTC-6, Nicholas Chen (DFP API Team) wrote:

Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 13, 2014, 2:08:45 AM5/13/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi David,

We're actually not using the pure suds implementation (so that might not be 100% relevant), we're using a fork of suds-jurko.

That said, I trust your proxy is setup properly, what's unclear - and this is a broader implementation type question that we're looking into. In any case where you've set up an https proxy in the middle, error 51 network is unreachable, then I believe you're breaking the SSL handshake between yourself and DFP. From testing, it seems that passing in an http:// proxy to the https constructor (yes I realize this is counter-intuitive), then the traffic should get forwarded along without ever breaking that handshake. We're looking into whether or not this is the best thing to do now.

Best,

Nicholas Chen, DFP API Team

David Rager's profile photo

David Rager

unread,
May 14, 2014, 2:23:59 AM5/14/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show error 51 network is unreachable message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Is that something I can try on my end?  Which constructor in particular should I try modifying, if so? 

Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 14, 2014, 6:49:50 PM5/14/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this error 51 network is unreachable or you need the view member email addresses permission to view the original message

to [email protected]

Yes, the same way you're passing in an https server as a proxy, you can pass in an http server to the https_proxy argument.

You can do this by manually instantiating your dfp_client OR by having your googleads.yaml file contain an 'https_proxy' arg that maps to an http server.

Best,

Nicholas Chen, DFP API Team

David Rager's profile photo

David Rager

unread,
May 15, 2014, 1:11:07 AM5/15/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]


Nicholas - I may not be following you.  I tried this:  

      proxy = {}

proxy['http'] = 'http://proxyserver:1234'

proxy['https'] = 'http://proxyserver:1234'

      client = suds.client.Client(self._SOAP_SERVICE_FORMAT % (server, error 51 network is unreachable, version, service_name),proxy=proxy)

That still returned auth errors and <urlopen error Tunnel connection failed: 404 Not Found>

Were you indicating a different method of wiring up an http server?

David Rager's profile photo

David Rager

unread,
May 15, 2014, 2:54:43 AM5/15/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

I believe I had luck by removing the https_proxy from the GoogleRefreshTokenClient, including it in the client call and just sending in the proxy['http'] to the suds.client.Client constructor.

Still need to test some more tomorrow - let me know if that sounds close to what you were indicating.  

Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 15, 2014, 6:31:46 PM5/15/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi David,

That's not quite what I was thinking (removing it from the GoogleRefreshTokenClient), but the second part is what I was after, passing the proxy to suds - I think you'd get the same effect if you set the address in your googleads.yaml (it should flow down through the dfp_client constructor). For whatever reason, it seems like the refresh isn't happening when your proxy is being included on the request for OAuth (and OAuth alone).

Best,

Nicholas Chen, DFP API Team

David Rager's profile photo

David Rager

unread,
May 15, 2014, 8:41:29 PM5/15/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Thank you for the help and the tip on googleads.yaml - appreciate your time.  

David Rager's profile photo

David Rager

unread,
May 16, 2014, 1:07:40 AM5/16/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Flipped to the yaml with no better luck.  My hack doesn't appear to be working ATM either.  

Do you have any suggestions on how to debug this with my IT folks?

Nicholas Chen (DFP API Team)'s profile photo

Nicholas Chen (DFP API Team)

unread,
May 16, 2014, 7:23:55 Error 51 network is unreachable to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

Hi David,

To be clear, my suggestion was to include testing an http served proxy (passed in under the guise of an https proxy) to at least allow you to pass the requests through a proxy. I had also tested this with a squid proxy / ssl bump enabled for an https server, but I'm not sure how your IT team would set that up on their end:

http://wiki.squid-cache.org/Features/SslBump

But this is effectively man-in-the-middling the request and isn't necessarily better than passing in an http intermediate proxy server.

Best,

Nicholas Chen, DFP API Team