[RESOLVED] Maniaplanet is crashing while loading the titles screen (online mode)

[nighthawk4571]

That '443' still bugs me.

1. From your log (sample line):

Code: Select all

[Net] {10 140} NetHttpClient::Request POST relay02.v04.maniaplanet.com:443 game/request.php?session_id=8638594&request_id=4 (data = 685 bytes)
[MasterServer] {10 140} Request sent : GetStatsAndAchievements (relay02.v04.maniaplanet.com:443)

This is sending a request. I see no sign of a reply.

2. From my log (sample line):

Code: Select all

[Net] {128 231}  Headers(1) for https://relay02.v04.maniaplanet.com/game/request.php?session_id=8612543&request_id=22: HTTP/1.1 200 OK

Here is a request and a reply (HTTP/1.1 200 OK).

It is obscure, but my new suspect is a failed SSL request to the relay02.v04 server. Of course, SSL relies upon certificates, which need to match the client with the server to allow onforwarding to various (server-based) services. To me, this seems an unlikely scenario with a Maniaplanet host server. So I ask, is your router or some other device or system software blocking these outgoing requests? Is your firewall really allowing Maniaplanet to talk via the net, both outgoing AND incoming, particularly for chat?

Does this point at least give a clue? I think I am heading into a difficult area here, beyond my regular analytical skills, so maybe this is proof that I simply cannot see the problem - cannot offer a solution - because I've reached the limit of my stupidity...

But The '443' thing still tells me there's a faulty file or process somewhere, which brings me back to (possibly) net-related Windows or MP system files.

Sorry mate . ( Resumes banging head on walls ).

Cheers .....

PS: I wonder what this is about:

Code: Select all

[Net] {11 133} NetHttpClient::Request GET s3-eu-west-1.amazonaws.com:443 /maniaplanet-4-profilechunks/34186/

(amazonaws.com, also with a 443 suffix)? Is this a cloud service which NADEO use? I've never noticed this in any of my logs.

[Miss]

Yes, they use AWS for their big data storage.

[TMarc]

interesting thoughts with the port 443.
I have just checked, 443 is not used and also not blocked after startup of Windows 10.
For testing, I have set my PC to get unfiltered access to the internet in the Fritzbox, but it did not help either.

Using netstat -na I can see many requests active using :443, mostly some Windows / Microsoft services.
And I'm also able to login to the player page using the webbrowser and https:// connection, which also uses Port 443.

I had one thought: I used the second ethernet port of my mainboard by error, but switching back to the first port did not help either.

So this leads me to the conclusion that it is either related to the later Windows 10 updates and an option I'm not aware of,
or that my Maniaplanet profile is buggy online.

Also changing the distro between beta and release did not help.

However, Maniaplanet should not crash like that

[nighthawk4571]

OK, that's one more theory gone into the bin. More thought needed. We are both still sane (sort of in my case) and you are at least able to play. So we shouldn't give up yet.

On the other hand, fate may hand you a solution: As you know, there have been a few small game updates over the past week or so. Maybe another one will inadvertently fix your issue (i.e.if it is indeed within the Maniaplanet package).

Cheers for now .....

[TMarc]

Unfortunately the issue persits with the latest updates.

Starting Maniaplanet in online mode crashes.
Starting Maniaplanet in silent or offline mode is working fine.
But it crashes whenever I enable the chat.

This is really weird.
A crash log does not exist, and the debug log is just cut...

[TMarc]

Today I took the time to check my router and my PC network connection stuff.

Port forwarding is enabled for both TCP and UDP on the ports 2350 and 3450.
Maniaplanet is allowed for all ports and all types in the Windows firewall.
I tried different compatibility modes, I tried network diagnostics, nothing helped.

I found a small network port monitoring tool which allows to filter for applications.

Whenever Maniaplanet tries to access the chat server, it crashes.

In the log of the tracing app it is: chatfront.v04.maniaplanet.com on port 5222.

Is there an additional port I would need to open in my router for that?

[Miss]

Forwarding ports won't help you here.

You say that the MP4.1 beta setup works fine for you - so have you tried completely removing/renaming your entire Documents/Maniaplanet folder, instead of only clearing the cache and removing your profile gbx file?

Also try completely deleting/renaming ProgramData/Maniaplanet.

[TMarc]

yes, I did. I removed everything and took the full setup. Did not help.

I don't know, perhaps some other tool or service is blocking. Perhaps I would need a clean windows install some day.

But I would also expect that the game tells if any necessary port is busy, and not just crashes (without even a crashlog sadly).

[TMarc]

At least it looks like it is a specific problem with my main PC.

Yesterday I downloaded the latest full setup and installed it on my laptop today, which has Intel HD and a Radeon mobile chip, and where I had installed Windows 10 about a year ago.
There is not much stuff on it, just Avira antivirus, Firefox and Irfanview.
Yesterday I did an update of the PC to Windows 10 1903 version (you see how long I did not use it, the battery seems to be dead ),
and finally just installed Maniaplanet and launched it with my regular account.

What shall I say, the chat is fully functional there No crash of Maniaplanet

But I defintely can't play on the laptop, Maniaplanet only sees the intel HD 3000 chip, Canyon runs on A01 with about 15 fps.

Today it shows an update to Windows 10 1909 which i'm installing now.
Let's see...

[nighthawk4571]

... Holding breath ..... Fingers crossed ...