Miasma Community

General Zone => Helpdesk => Topic started by: nasty on November 20, 2025, 17:26

Title: Unable to connect to miasma| freon
Post by: nasty on November 20, 2025, 17:26
Hello, fellas!
Cant get in to the game for approx last few weeks. I think it bcause of we are being disconnected from external web. Foreign servers not avalible anymore.
replacing .u files didnt help.
When trying to connect, the screen displays "ut2004://37.187.146.47/index.ut2" and nothing happens.
Anybody have the same problem?
Title: Re: Unable to connect to miasma| freon
Post by: Nardaq_NL on November 20, 2025, 19:36
can you ping the server?

how is your trace (tracert in windows) to the mia server looks like?
Title: Re: Unable to connect to miasma| freon
Post by: Piglet on November 24, 2025, 15:24
He can definitely reach the machine....as this site is hosted on it....

Please can you paste in contents of UT2004.log after trying to connect?
Title: Re: Unable to connect to miasma| freon
Post by: nasty on November 25, 2025, 17:25
Yes, i can ping server's ip:
ping 37.187.146.47
data packages: sent = 4, recieved = 4, lost = 0

log:
Log: Log file open, 11/26/25 00:14:37
Init: Name subsystem initialized
Init: Detected: Microsoft Windows NT 6.2 (Build: 9200)
Init: Version: 3369 (128.29)
Init: Compiled: Nov 23 2005 16:23:34
Init: Command line:
Init: Character set: Unicode
Init: Base directory: C:\Games\Unreal Tournament 2004\System\
Init: Ini:UT2004.ini   UserIni:User.ini
Init: Build label: UT2004 Build UT2004_Build_[2005-11-23_16.22]
Init: Object subsystem initialized
Log: Splash screen filename is '..\Help\UT2004Logo.bmp'
Log:    nvldumd.dll/NVIDIA GeForce GTX 1060 6GB
Log: Game class is 'GameInfo'
Log: Bringing Level Entry.myLevel up for play (0) appSeconds: 1.401000...
ScriptLog: GameInfo::InitGame : bEnableStatLogging False
Error: Favorites::ImportText: Bad termination in: (ServerID=0,IP="37.187.146.47",Port=9777,QueryPort=9778,ServerName="@@@[яяMс
Log: Browse: NoIntro.ut2?Name=Nasty_(RU)?Class=Engine.Pawn?Character=Kane?team=255?Sex=M?SpectatorOnly=1
Log: Collecting garbage
Log: Purging garbage
Log: Garbage: objects: 27620->27620; refs: 280382
Log: Game class is 'CinematicGame'
Log: Bringing Level NoIntro.myLevel up for play (0) appSeconds: 1.888000...
ScriptLog: GameInfo::InitGame : bEnableStatLogging False
Progress: Loading VehicleInvasion-105...
Warning:   'VehicleInvasion-105':    'VehicleInvasion-105'
Warning:   :    'VehicleInvasion-105'
Warning: Error loading VehicleInvasion-105 !!!
Progress: Loading Haloscript...
Warning:   'Haloscript':    'Haloscript'
Warning:   :    'Haloscript'
Warning: Error loading Haloscript !!!
Progress: Loading UT2004RPG...
Warning:   'UT2004RPG':    'UT2004RPG'
Warning:   :    'UT2004RPG'
Warning: Error loading UT2004RPG !!!
Progress: Loading ArkonShields...
Warning:   'ArkonShields':    'ArkonShields'
Warning:   :    'ArkonShields'
Warning: Error loading ArkonShields !!!
Progress: Loading ASX...
Warning:   'ASX':    'ASX'
Warning:   :    'ASX'
Warning: Error loading ASX !!!
Progress: Loading Dragonfly...
Warning:   'Dragonfly':    'Dragonfly'
Warning:   :    'Dragonfly'
Warning: Error loading Dragonfly !!!
Progress: Loading edo_chute1...
Warning:   'edo_chute1':    'edo_chute1'
Warning:   :    'edo_chute1'
Warning: Error loading edo_chute1 !!!
Progress: Loading InvasionEverywere2...
Warning:   'InvasionEverywere2':    'InvasionEverywere2'
Warning:   :    'InvasionEverywere2'
Warning: Error loading InvasionEverywere2 !!!
Progress: Loading LightSuit...
Warning:   'LightSuit':    'LightSuit'
Warning:   :    'LightSuit'
Warning: Error loading LightSuit !!!
Progress: Loading Matrix2004_v130...
Warning:   'Matrix2004_v130':    'Matrix2004_v130'
Warning:   :    'Matrix2004_v130'
Warning: Error loading Matrix2004_v130 !!!
Progress: Loading MutFallDamage...
Warning:   'MutFallDamage':    'MutFallDamage'
Warning:   :    'MutFallDamage'
Warning: Error loading MutFallDamage !!!
Progress: Loading NoVehicleLocks...
Warning:   'NoVehicleLocks':    'NoVehicleLocks'
Warning:   :    'NoVehicleLocks'
Warning: Error loading NoVehicleLocks !!!
Progress: Loading Radar2004...
Warning:   'Radar2004':    'Radar2004'
Warning:   :    'Radar2004'
Warning: Error loading Radar2004 !!!
Progress: Loading TA100...
Warning:   'TA100':    'TA100'
Warning:   :    'TA100'
Warning: Error loading TA100 !!!
Progress: Loading UT2005Navy...
Warning:   'UT2005Navy':    'UT2005Navy'
Warning:   :    'UT2005Navy'
Warning: Error loading UT2005Navy !!!
Progress: Loading utcompv17a...
Warning:   'utcompv17a':    'utcompv17a'
Warning:   :    'utcompv17a'
Warning: Error loading utcompv17a !!!
Progress: Loading UTV2004SA...
Warning:   'UTV2004SA':    'UTV2004SA'
Warning:   :    'UTV2004SA'
Warning: Error loading UTV2004SA !!!
Progress: Loading VividVehicles...
Warning:   'VividVehicles':    'VividVehicles'
Warning:   :    'VividVehicles'
Warning: Error loading VividVehicles !!!
Log: ALAudio: Couldn't find a means to record audio.
ScriptLog: New Player Nasty_(RU) id=f79a957444e7279940699461ae9d10df
Log: Opened viewport
Log: Enter SetRes: 1680x1050 Fullscreen 1
Log: Using back-buffer format 22(32-bit)
Log: Using depth-buffer format 77(32-bit)
Log: Creating device
Log: xD3DHelper::Init (QuadEmulation)
Log: Startup time: 2.231000 seconds
Log: Precaching: NoIntro.LevelInfo0
Log: Static mesh batches: 0 vertex bytes, 0 index bytes
Log: Allocating 16384 byte dynamic index buffer.
Log: Finished precaching geometry in 0.010 seconds
Log: Finished precaching textures in 0.000 seconds
Debug: UT2k4MainMenu.Opened()   Sender:Package.UT2k4MainMenu
Log: URL: Adding default option Name=Nasty_(RU)
Log: URL: Adding default option Class=Engine.Pawn
Log: URL: Adding default option Character=Kane
Log: URL: Adding default option team=255
Log: Browse: Index.ut2?disconnect?Name=Nasty_(RU)?Class=Engine.Pawn?Character=Kane?team=255
Log: ;   
ScriptLog: UT2k4MainMenu NotifyLevelChange  PendingConnection:False
Log: GP=FALSE
Log: Spawning new actor for Viewport WindowsViewport
ScriptLog: New Player Nasty_(RU) id=f79a957444e7279940699461ae9d10df
Log: Static mesh batches: 0 vertex bytes, 0 index bytes
Log: FIREWALL: Freed XP.SP2 Firewall Object
IRC: 2 Servers 0 Channels
Log: Defaulting to false
ScriptLog: UT2k4Browser_ServerListPageFavorites Spawned new ServerQueryClient 'Entry.ServerQueryClient'
Log: Defaulting to false
Log: Resolving utmaster.openspy.net...
Log: Resolved utmaster.openspy.net -> 134.122.16.249
Debug: UT2k4MainMenu.Opened()   Sender:None
ScriptLog: PreClientTravel
Log: URL: Adding default option Name=Nasty_(RU)
Log: URL: Adding default option Class=Engine.Pawn
Log: URL: Adding default option Character=Kane
Log: URL: Adding default option team=255
Log: Browse: 37.187.146.47:5777/Index.ut2?Name=Nasty_(RU)?Class=Engine.Pawn?Character=Kane?team=255
Log: Resolving utmaster.openspy.net...
Log: Resolved utmaster.openspy.net -> 134.122.16.249
Log: Connection established.
ScriptLog: PreClientTravel
Log: URL: Adding default option Name=Nasty_(RU)
Log: URL: Adding default option Class=Engine.Pawn
Log: URL: Adding default option Character=Kane
Log: URL: Adding default option team=255
Log: Browse: 37.187.146.47:9777/Index.ut2?Name=Nasty_(RU)?Class=Engine.Pawn?Character=Kane?team=255
NetComeGo: Close TcpipConnection 37.187.146.47:5777 11/26/25 00:14:54
Exit: Socket shut down
Log: Resolving utmaster.openspy.net...
Log: Resolved utmaster.openspy.net -> 134.122.16.249
Log: Connection established.
ScriptLog: PreClientTravel
Log: URL: Adding default option Name=Nasty_(RU)
Log: URL: Adding default option Class=Engine.Pawn
Log: URL: Adding default option Character=Kane
Log: URL: Adding default option team=255
Log: Browse: 37.187.146.47:9777/Index.ut2?Name=Nasty_(RU)?Class=Engine.Pawn?Character=Kane?team=255
NetComeGo: Close TcpipConnection 37.187.146.47:9777 11/26/25 00:15:07
Exit: Socket shut down
ScriptLog: PreClientTravel
Log: URL: Adding default option Name=Nasty_(RU)
Log: URL: Adding default option Class=Engine.Pawn
Log: URL: Adding default option Character=Kane
Log: URL: Adding default option team=255
Log: Browse: 37.187.146.47:5777/Index.ut2?Name=Nasty_(RU)?Class=Engine.Pawn?Character=Kane?team=255
NetComeGo: Close TcpipConnection 37.187.146.47:9777 11/26/25 00:15:20
Exit: Socket shut down
Log: appRequestExit(0)
Exit: Preparing to exit.
Log: Purging garbage
Log: Unbound to Window.dll
Log: Unbound to Core.dll
Log: Unbound to Engine.dll
NetComeGo: Close TcpipConnection 37.187.146.47:5777 11/26/25 00:17:00
Exit: Socket shut down
Exit: Game engine shut down
Log: Unbound to WinDrv.dll
Exit: Windows client shut down
Log: Unbound to D3DDrv.dll
Log: Unbound to XGame.dll
Log: Unbound to IpDrv.dll
Log: Unbound to Editor.dll
Log: Unbound to Fire.dll
Log: Unbound to XInterface.dll
Log: Unbound to UWeb.dll
Log: Unbound to Onslaught.dll
Log: Unbound to ALAudio.dll
Log: Waiting for file streaming thread to finish...
Exit: OpenAL Audio subsystem shut down.
Log: Garbage: objects: 32381->0; refs: 280382
Exit: Object subsystem successfully closed.
Exit: Exiting.
Log: FileManager: Reading 0 GByte 54 MByte 782 KByte 310 Bytes from HD took 0.682996 seconds (0.641996 reading, 0.041000 seeking).
Log: FileManager: 0.201000 seconds spent with misc. duties
Uninitialized: Name subsystem shut down
Uninitialized: Memory Allocation Status
Uninitialized: Curr Memory  0.253M /  3.184M
Uninitialized: Peak Memory  71.159M /  73.035M
Uninitialized: Allocs         673 Current /  49035053 Total
Uninitialized: Log file closed, 11/26/25 00:17:01
Title: Re: Unable to connect to miasma| freon
Post by: zeus on November 27, 2025, 22:05
This is more than likely caused by a country specific and very internal ruleset (as written in the 1st post) -> "web" is safe to browse, other random ports are sketchy and are automatically blocked.
HYDRO had a similar scenario few years ago, where he was unable to connect to the servers for about 8 months.
Title: Re: Unable to connect to miasma| freon
Post by: Piglet on November 28, 2025, 14:50
I've had another Russian player found that all communication on port 7777 has been blocked by their ISP. They have used a proxy to successfully get through and play.

Like Zeus said, I suspect this is what's happening to you too.

Title: Re: Unable to connect to miasma| freon
Post by: Vidmal on December 12, 2025, 21:21
Hey m8, try the ZAPRET DISCORD YOUTUBE package, it helped me today
Title: Re: Unable to connect to miasma| freon
Post by: Natalia on December 18, 2025, 18:31
Hi, I can't access the server. It won't load at all. What should I do?
Title: Re: Unable to connect to miasma| freon
Post by: Piglet on December 18, 2025, 21:51
Hi, are you still having problems? I thought I updated something that would let you connect.

Title: Re: Unable to connect to miasma| freon
Post by: Pyc on January 08, 2026, 19:42
Hey, I had this issue several times, last time a couple of days ago. Looks like my ISP turned on some temporarily restrictions because a UDP based VPN stopped working at the same time. I was able to connect though another VPN, but I got disconnected for using a proxy.
Title: Re: Unable to connect to miasma| freon
Post by: NAF-NAF(RU) on January 10, 2026, 19:23
I can't access your website since the new year. I can only access it through a VPN. However, you are blocking me through the VPN. I am writing this through a translator.
Title: Re: Unable to connect to miasma| freon
Post by: Pyc on January 10, 2026, 20:04
Piglet, any chance you allow playing with VPN?
Title: Re: Unable to connect to miasma| freon
Post by: Piglet on January 11, 2026, 11:46
Hiya, I fixed it for you before you asked yesterday. Please let me know whether you're able to connect now.
Title: Re: Unable to connect to miasma| freon
Post by: Pyc on January 11, 2026, 12:31
Quote from: Piglet on January 11, 2026, 11:46
Hiya, I fixed it for you before you asked yesterday. Please let me know whether you're able to connect now.

Thank you! Look like now I can use VPN.

Yesterday after one game finished I was unable to connect to the next one. So I experimented with DPI bypass tools and then successfully connected. But I'm not sure what helped. I will write here if I experience this issue again.
Title: Re: Unable to connect to miasma| freon
Post by: NAF-NAF(RU) on January 14, 2026, 15:39
I want to say thank you! Now I can access the Mia server via VPN.
Title: Re: Unable to connect to miasma| freon
Post by: Piglet on January 14, 2026, 22:44
:) Let's hope this war insanity stops soon so we can go back to all being friends. In the mean time, we can play games when we can.
Title: Re: Unable to connect to miasma| freon
Post by: RES on January 15, 2026, 00:40
Hello, Piglet. I didn't want to start a new thread, so I'll write here. I'm having problems connecting to the server. Nothing happens when I connect. Maps and updates aren't downloading. I tried clearing the cache, but that didn't help. What should I do? Thanks for your attention.

[linkimg]https://ibb.co/B2XbdBqs[/linkimg]

PING 37.187.146.47 (37.187.146.47): 64 data bytes
Reply from 37.187.146.47:  bytes=64  ttl=53  seq=1  time=47.644 ms
Reply from 37.187.146.47:  bytes=64  ttl=53  seq=2  time=47.669 ms
Reply from 37.187.146.47:  bytes=64  ttl=53  seq=3  time=47.631 ms
Reply from 37.187.146.47:  bytes=64  ttl=53  seq=4  time=47.718 ms

--- Ping Statistic "37.187.146.47" ---
Packets: Sent=4, Received=4, Lost=0 (0.00% loss)
Round-trip min/avg/max = 47.631/47.665/47.718 ms

traceroute to 37.187.146.47, 20 hops max, 38 byte packets
1  10.126.16.1 (10.126.16.1)  0.910 ms  0.804 ms  0.874 ms
2  juni-vl-149-ecmp-avt.setel.ru (80.253.16.197)  1.065 ms  1.121 ms  0.937 ms
3  juni-lo-0-m9.setel.ru (80.253.16.9)  1.712 ms  1.975 ms  1.673 ms
4  msk-m9-b1-ae6.fiord.net (62.140.245.1)  40.353 ms  40.633 ms  124.570 ms
5  warsaw-lim-b1-ae5-vlan3650.fiord.net (80.77.167.153)  36.426 ms  36.947 ms  36.766 ms
6  waw-wa1-pb1-nc5.pl.eu (91.121.131.46)  46.204 ms  43.726 ms  43.938 ms
7  *  *  *
8  *  *  *
9  *  *  213.251.128.112 (213.251.128.112)  42.775 ms
10  *  *  *
11  be104.lil2-gra1-sbb1-nc5.fr.eu (213.186.32.210)  48.422 ms  48.769 ms  be104.lil2-gra1-sbb2-nc5.fr.eu (213.251.128.66)  47.807 ms
12  37.59.16.28 (37.59.16.28)  49.650 ms  37.59.16.40 (37.59.16.40)  51.908 ms  37.59.16.32 (37.59.16.32)  50.418 ms
13  *  *  *
14  *  *  *
15  *  *  *
16  *  *  *
17  mx1.miasma.rocks (37.187.146.47)  47.596 ms  47.536 ms  47.688 ms
Trace Complete.
Title: Re: Unable to connect to miasma| freon
Post by: RES on January 15, 2026, 01:04
It seems I've figured out the problem and can log in using the DPI service. I'm deleting my previous post. Thank you.
Title: Re: Unable to connect to miasma| freon
Post by: Piglet on January 15, 2026, 08:16
If the DPI service gives lag then other people have used VPN. I can allow that at this end for you on the game server - but it may not be allowed at your end.
Title: Re: Unable to connect to miasma| freon
Post by: RES on January 15, 2026, 22:37
Everything works as before, I hope it stays that way. I apologize for the inconvenience. Thank you.
Title: Re: Unable to connect to miasma| freon
Post by: Pyc on January 16, 2026, 17:22
Quote from: Piglet on January 14, 2026, 22:44
:) Let's hope this war insanity stops soon so we can go back to all being friends. In the mean time, we can play games when we can.
Well said, I hope we will see that time.
Title: Re: Unable to connect to miasma| freon
Post by: KoTELLO on March 27, 2026, 18:48
Hello!

Did someone play with the "zapret" only without using vpn? Is everything working for you now? I haven't been able to connect for about a couple of weeks  :(
Title: Re: Unable to connect to miasma| freon
Post by: Pyc on March 27, 2026, 19:10
I have same problem. It worked before, but stopped some weeks ago.
Title: Re: Unable to connect to miasma| freon
Post by: Piglet on March 31, 2026, 09:16
I'm sorry that we can't help you.

You're being affected by local Russian regulations being put in place by your ISP. Some people appear to be getting around them using VPNs.
Title: Re: Unable to connect to miasma| freon
Post by: Pyc on March 31, 2026, 10:56
Yep, only VPN works at the moment. But I'm experimenting with Zapret from time to time to find a way for a direct connection.