1.20.4 MC 1.20.4 Forge 49.0.14 connection issues.

[Guest]

I'm hosting a multiplayer server in my local network.
I use cloudflare DNS to point my domain to a ngrok tunnel address which tunnels into my network for an added layer of security. (no port forwards on router)
The Server is loaded with Forge 49.0.14 and I have started it with forge-1.20.4-49.0.14-shim.jar.
Connecting with a vanilla client works flawlessly.
I'm only using Forge server side for Discord integration.

I've loaded a few client sided mods for testing through the curseforge app.
However the game can not longer resolve my domain name.
When I load back into vanilla client it works again.

Client info:
Minecraft 1.20.4
Forge 49.0.14
Mods: Journey Map

connecting via the tunnel URL works and I can connect.
Is anyone able to assist getting the domain URL working please?

Brief description of the redirects:
localhost:25565>ngrok.io:12345>play.domain.com
 

[Paint_Ninja]

Please share your debug.log, as explained in the FAQ 

[Guest]

There is no debug logs as I cannot resolve the server address to generate logs

[Guest]

[13:51:02] [Server Pinger #0/ERROR]: Failed to initialize SRV redirect resolved, some servers might not work
javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.dns.DnsContextFactory
	at javax.naming.spi.NamingManager.getFactory(NamingManager.java:762) ~[?:?]
	at javax.naming.spi.NamingManager.lambda$getInitialContext$1(NamingManager.java:724) ~[?:?]
	at jdk.internal.loader.AbstractClassLoaderValue$Memoizer.get(AbstractClassLoaderValue.java:329) ~[?:?]
	at jdk.internal.loader.AbstractClassLoaderValue.computeIfAbsent(AbstractClassLoaderValue.java:205) ~[?:?]
	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:724) ~[?:?]
	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305) ~[?:?]
	at javax.naming.InitialContext.init(InitialContext.java:236) ~[?:?]
	at javax.naming.InitialContext.<init>(InitialContext.java:208) ~[?:?]
	at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:130) ~[?:?]
	at net.minecraft.client.multiplayer.resolver.ServerRedirectHandler.m_171895_(ServerRedirectHandler.java:33) ~[forge-1.20.4-49.0.14-client.jar!/:?]
	at net.minecraft.client.multiplayer.resolver.ServerNameResolver.<clinit>(ServerNameResolver.java:8) ~[forge-1.20.4-49.0.14-client.jar!/:?]
	at net.minecraft.client.multiplayer.ServerStatusPinger.m_105459_(ServerStatusPinger.java:48) ~[forge-1.20.4-49.0.14-client.jar!/:?]
	at net.minecraft.client.gui.screens.multiplayer.ServerSelectionList$OnlineServerEntry.m_99900_(ServerSelectionList.java:242) ~[forge-1.20.4-49.0.14-client.jar!/:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
	at java.lang.Thread.run(Thread.java:833) ~[?:?]
Caused by: java.lang.IllegalAccessException: class javax.naming.spi.NamingManager (in module java.naming) cannot access class com.sun.jndi.dns.DnsContextFactory (in module jdk.naming.dns) because module jdk.naming.dns does not export com.sun.jndi.dns to module java.naming
	at jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:392) ~[?:?]
	at java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:674) ~[?:?]
	at java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:489) ~[?:?]
	at java.lang.reflect.ReflectAccess.newInstance(ReflectAccess.java:128) ~[?:?]
	at jdk.internal.reflect.ReflectionFactory.newInstance(ReflectionFactory.java:347) ~[?:?]
	at java.lang.Class.newInstance(Class.java:645) ~[?:?]
	at javax.naming.spi.NamingManager.getFactory(NamingManager.java:759) ~[?:?]
	... 18 more

This is from latest.log

Edited January 8 by Toadie

[Paint_Ninja]

Please read the FAQ to find out how to enable the debug.log, where to find it and how to upload it to a paste site to share a link. The debug.log will contain various troubleshooting details when attempting to connect, including what IP stack it picked, what the DNS query resolved to, where in the connection process it failed and more.

[Guest]

1 hour ago, Paint_Ninja said:

Please read the FAQ to find out how to enable the debug.log, where to find it and how to upload it to a paste site to share a link. The debug.log will contain various troubleshooting details when attempting to connect, including what IP stack it picked, what the DNS query resolved to, where in the connection process it failed and more.

Ok, so we can both agree im dumb and move on... Sorry!
https://pastebin.com/31s9duKW

[Paint_Ninja]

Thanks, seems to be an edge-case bug with the new launch system introduced in Forge 1.20.3+.

A temporary workaround until we fix the issue is to add the following JVM arg:

--add-exports jdk.naming.dns/com.sun.jndi.dns=java.naming

 

[Guest]

that worked thank you