Troubleshooting

acffordyce973 edited this page Nov 6, 2016 · 56 revisions

PSO2Proxy Troubleshooting

This Wiki page has troubleshooting instructions for both Client and Server setup.

Please Note

  • PSO2Proxy is for the Japanese version of PSO2 only. The proxy will not work for the SEA version (from PlayPark) in its current form, and the public proxy is only for connecting to PSO2 JP.
  • PSO2Proxy will only work with the Tweaker. The manual method is no longer working and you will not be able to login.

IRC Support

If you have followed the steps for your specific issue and have been unable to fix it then please join our IRC Support Room using:

  • The Mibbit Web Client, or
  • A Native IRC Client; Server/Host: "irc.badnik.zone", Channel: "#pso2proxypublic"

Incompatible Applications

Always remember to disable your antivirus or add the 'pso2_bin' folder as an exception while troubleshooting any issue. We are aware of a few applications that are known to be incompatible with the proxy on the client-side, these are:

  • AVG Antivirus - Known to cause Gameguard errors. Try adding the entire PSO2 folder to exceptions, or disable AVG while playing.
  • Avira Antivirus - Known to block hosts file modifications. The option "Protect Windows hosts file from changes" can be disabled in Extras > Configuration > General > Security.
  • Webroot Antivirus - Blocks hosts file modifications. The option "Prevent any program from modifying the HOSTS file" can be disabled in Settings > Shields.
  • Kaspersky Antivirus - Known to block hosts file modifications. Exiting the Application then modifying the hosts file should fix this. Remember to start the Application after.
  • Panda Antivirus - Causes GameGuard issues (NP0/NP1002). Adding the 'pso2_bin' folder to exceptions should fix this.
  • Dolby Axon - Causes a timeout when attempting to connect. Close or uninstall this application before playing.
  • Certain Razer Applications - Some Razer applications come with a DLL that interferes with the proxy DLL. Try disabling, closing, or uninstalling these applications.
  • Tunngle - Causes a timeout when attempting to connect. Close or uninstall this application before playing.

Client Setup and Connection Troubleshooting

GameGuard displays an NP#### error when launching

This error frequently happens when GameGuard freaks out, which a lot of things can cause because of the way the proxy DLL works. Here are some general troubleshooting steps:

  1. Delete the "Plugins" folder and "pso2h.dll" from "pso2_bin". This will cause the Tweaker to download the latest injector when opened. Make sure that the "PSO2Proxy" plugin is enabled in the Tweaker before starting the game. If you do not see this plugin then your Antivirus may have deleted it.

  2. If you use any application that HOOKS into a program (antivirus, FRAPS, SweetFX, MSI Afterburner, etc.), disable the software and try launching the game again. If you can, try running JUST PSO2 with nothing else running in the background to rule out any other software.

  3. Try to use the "Fix GameGuard Errors" option in PSO2Tweaker under troubleshooting or follow this /r/pso2 wiki guide.

  4. Try launching PSO2 without the proxy configured. An outdated version of PSO2 or corrupted game files could cause an incompatibility with the proxy DLL trying to inject for the wrong version. If this works, then check all files using the old method from within PSO2 Tweaker Orb Menu.

Ships show as 'Unknown', Error 249, or Tweaker reports connection test failed

This error happens when PSO2 can't connect to any ship to query it. Usually this means the hosts file isn't working or you are using a VPN program (e.g. Softether) which is causing connection issues. Here are some steps you can take to troubleshoot:

  1. In command prompt, run ping cloud02.cyberkitsune.net, then ping gs001.pso2gs.net and check the results. If both servers ping back, then continue to troubleshooting step 2. If only the first address pings back, double check your hosts file has been modified, run ipconfig /flushdns in command prompt and try pinging again. If neither address pings back you have connectivity issues to the proxy server.

  2. Reset the winsock TCP stack as sometimes that may causes issues. First, create a system restore point just in case anything goes wrong. Then, open command prompt as administrator and run netsh winsock reset catalog and netsh int ip reset reset.log and then restart your computer.

  3. In some cases, some DSL ISPs have a packet overhead on top of their MTU and you must adjust your system MTU to compensate, to check if this applies to you:

Use the command ping google.com -f -l 1472 in a Command Prompt window. If the message Packet needs to be fragmented but DF set appears then you must adjust your MTU.

If your issue is still not resolved, contact us on IRC and we can attempt one of our hacks to fix it. If you have done the network diagnostic test then give the URL to whoever is helping you.

Connection timed out when trying to connect

If this error happens before you see "Authenticating SEGA ID", the RSA injector is off or has failed. This usually occurs due to three main reasons:

  • Your PSO2 installation is out of date or corrupt. Try using the "Check for PSO2 Updates" Old Method in the Tweaker before launching again.
  • An incompatible Application is interfering with the RSA Injector.
  • You do not have the latest version of the PSO2Proxy DLL or it is not enabled. Delete the "Plugins" folder and "pso2h.dll" from "pso2_bin". This will cause the Tweaker to download the latest plugin files when opened. Make sure that the "PSO2Proxy" plugin is enabled in the Tweaker before starting the game. If you do not see this plugin then your Antivirus may have deleted it.

If you are sure your game version is up to date and you do not have any of the incompatible Applications listed, then contact us on IRC and we can troubleshoot your issue.

If the error happens after "Authenticating SEGA ID" shows up and takes a while:

  • Try step 2 of the error 249 troubleshooting, reset Winsock TCP Stack.
  • Try step 3 of the error 249 troubleshooting, adjust your MTU.

Server Setup and Troubleshooting

exceptions.UnicodeEncodeError: 'ascii' codec can't encode characters in position...

UnicodeEncodeError usually occurs when your Server or SSH client/terminal does not have UTF-8 support. See here to change your locale on a Debian based system, or here for PuTTY configuration.

ImportError: cannot import name PKCS1_v1_5

The python-crypto package on this Ubuntu release is a lower version than what is needed and thus the required module PKCS1_v1_5.py is missing. It'll have to be grabbed manually as follows:

cd /opt
sudo apt-get install python-dev build-essential
git clone https://github.com/dlitz/pycrypto.git
cd pycrypto
git checkout v2.6.1
./configure
python setup.py build
sudo python setup.py install

To Do

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.