-
Notifications
You must be signed in to change notification settings - Fork 19
Troubleshooting
This page provides tips regarding common issues you might encounter while setting up this project.
You need to install Python, I recommend the latest version of Python 2.7:
-
https://www.python.org/downloads/release/python-2718/
- Pick the x86 MSI installer (even on a 64-bit PC).
You need to install a dependency called twisted as follows:
- Open a console cmd.exe or powershell.exe
- Type this command to install twisted:
C:\Python27\python.exe -m pip install twisted
-
OR
C:\Python27\Script\pip.exe install twisted
NB: If you are using multiple versions of Python, you might need to specify explicitly the complete path to the right python.exe program.
In other words, rather than writing python some_commands
, make sure
to write:
-
C:\Python27\python.exe some_commands...
- where you replace
C:\Python27\python.exe
with the location of your version of python. - This version of python must have twisted installed.
- where you replace
Some systems might enforce security policies to prevent the use of weak SSL security such as small keys, insecure algorithms, etc. For instance:
Setting LegacySSL = ON
in the config.ini
file might fix the issue.
Please make sure you are using the latest version of the server from
GitHub as well.
There are several ways to start the servers and some might not work depending on how your system is configured. The goal is to have the servers windows up and running like this for AltWFC and MH3SP servers:
Here are 2 ways to start the servers:
- Double-click on the server OR
- Open a console in the server folder and run it with python.
- Double-click on master_server.py in the
MH3SP
ANDdwc_network_server_emulator
folders. - NB: It will only work if the default version of Python on your system has the dependencies installed properly!
Opening a console in the server folder can be done in 2 ways:
- Type
cmd
(orpowershell
) in the address bar and press Enter.
- In the console, type
cd
(don't forget the space after "cd") then drag and drop the folder onto the console and press Enter. Then, execute the server using python. It should look like this for MH3SP servers:
NB: This process has to be done for each server (i.e. MH3SP and AltWFC)!
Just close all windows of the servers.
To connect on Wiimmfi again, you need to remove the network redirection. It will differ depending on the method you chose to redirect the network traffic.
- Remove each line containing
wiimmfi.de
in yourhosts
file- Alternatively, you can just add
#
at the start of these lines to make them ignored by the system.
- Alternatively, you can just add
hosts
file location:
-
Windows:
%SystemRoot%\system32\drivers\etc\hosts
-
Mac OS:
/private/etc/hosts
-
Linux:
/etc/hosts
- Close your DNS server.
- Remove your DNS IP address from the Wii's network connection settings.
When you try to connect online, the loading bar progress can provide valuable information:
- Stopped before 20%: Probably an Internet connection issue
- Stopped at 20%: A Nintendo NAS server issue
- Stopped at 75% and above: Most-likely a Capcom server issue
You might want to visit Wiimmfi site to have more details about the error codes you encounter:
- Error codes page: https://wiimmfi.de/error
The game can't connect to Nintendo NAS server. Make sure that:
- AltWFC's servers are running properly
- the redirection is done correctly
- AltWFC's IP address is
0.0.0.0
in the[NasServer]
section of thealtwfc_nas.cfg
config file - On a real Wii, you've set in the network settings your server IP address as a primary DNS.
- On a real Wii, the entries you've added in your hosts file match the IP address your DNS server is using (i.e. not 127.0.0.1)
Your game isn't patched properly and connect to official Nintendo servers.
- Make sure you've Wiimmfi-patched the game properly.
- https://wiimmfi.de/patcher (Wiimmfi ISO Patcher is preferred)
This is a Wii Shop error code, the NAND wasn't used to connect to
the Japanese MH3 online server. You need to copy the User/Wii
folder content to Dolphin's Wii
folder:
This is a Wii Shop error code, the NAND wasn't used to connect to the Japanese MH3 online server. The following workaround can be tried:
I documented some of the MH3 specific error codes in the MHTrIDA repository.
The game's can't resolve the server domain name:
- mmh-t1-opn02.mmh-service.capcom.co.jp (Japanese version)
- mmh-t1-opn03.mmh-service.capcom.co.jp (American version)
- mmh-t1-opn04.mmh-service.capcom.co.jp (European version)
Make sure these entries are in your hosts file and are resolved by your DNS server to a valid IP address (i.e. 127.0.0.1 is not a valid address for the Wii!).
Make sure that:
- MH3SP's servers are running properly
- the redirection is done correctly
- MH3SP's IP address in
config.ini
is valid (i.e. 127.0.0.1 is not a valid address for the Wii!). - On a real Wii, you've set in the network settings your server IP address as a primary DNS.
The game can't connect to the server IP address.
The server takes too long to respond.
The game can't establish the SSL connection to the Capcom server.
The Wii is using deprecated SSL security standards and can conflict
with OpenSSL and OS security policies. Setting LegacySSL = ON
in
the config.ini
file might fix the issue. Please make sure you are
using the latest version of the server from GitHub as well.
The in-game root CA certificate is invalid. Make sure you have patched the game with a valid root CA and that the server you're connecting to is using the server certificate associated with this root CA. These errors can also happen if the Wii is reporting an incorrect date or is using a corrupted (c)IOS.
NB: This shouldn't happen with MH3SP's default certificates.
SSL handshake failure: invalid CN (Common Name).
SSL handshake failure: invalid Root CA (Certificate Authority).
SSL handshake failure: invalid Certificate Chain.
SSL handshake failure: invalid Date. This error 11607 should NEVER happen in normal circumstances using a valid certifcate. Make sure the Wii's date is correct. If it's, then, you most likely (had) used a hacking method that corrupted the (c)IOS used to launch the game. Before trying anything, these attempts to fix the error 11607 are a risky process, so do it at your own risk!
Attempts to fix EC 11607
- Backup everything
- Install BootMii on boot2, if possible
- Create a backup of the NAND using BootMii
- Run SysCheck
- Check the report file generated on the SD card
- Make sure the report file is reporting the right date
- Make sure the Wii is using IOS versions matching your System Menu version
- Fix the corrupted IOS (the simple way)
- Perform a factory reset
- Hack your Wii again using a safe method not installing junks
- Restore the save from your NAND backup
- Fix the corrupted IOS (the hard way, untested)
- Install official IOS versions for: (can brick your Wii if you mess up)
- the current System Menu version
- the IOS base for cIOS like (IOS: 36, 37, 38, 56, 57, 58, 60)
- Reinstall your cIOS using sane IOS bases
- Install official IOS versions for: (can brick your Wii if you mess up)
The server didn't answer to the game. You probably are using a feature that isn't supported by the server yet.