Unable to use domain instead of IP?

[N-Montana]

Bug description

I'm currently in the process of migrating my server to be a domain instead of direct IP for security issues, however it seems I am unable to have automodpack recognize the domain. No matter what when attempting to connect via the domain it gives an error and the server gives the following:

The error seems to suggest that using a domain can be done but I'm unable to figure out exactly how to set it up.

Steps to reproduce

1. Attempt to set automodpack to use a server domain
2. Try to join the server via domain, resulting in the error

Expected behavior

No response

Actual behavior

No response

Relevant logs

No response

Minecraft & Mod Loader versions

1.18.2 Forge 40.2.21

Minecraft launcher

No response

Operating system

Unknown (Server is 3rd party hosted)

AutoModpack version

4.0.0 beta18

Other information

No response

Check list

• I have verified that the issue persists in the latest version of the mod.
• I have searched the existing issues and confirmed that this is not a duplicate.

[Skidamek]

Do you use cloudflare dns proxy option? I recently got report that this somehow breaks automodpack host.

[Skidamek]

if thats the case please try latest dev build artifact its untested may not work but i changed slightly server host handling

[N-Montana]

I believe we are (I'm not handling that side personally), I'll test it when I get a chance. Thanks for the quick response!

[N-Montana]

Sorry it took a while to test it, it seems to be giving the same issue. I'm assuming that the domain just goes into the "Host IP" config space?

[Skidamek]

Yes and localHostIp too. But if empty client will try to get modpack from where it connected to Minecraft server that's why it's optional.

[N-Montana]

Okay just wanted to make sure, it does just fail with the same error even when the IP is left blank.

[Skidamek]

Well that's unfortunate then, I don't have any other solution for you at the moment however I plan to make major rework of modpack host which should fix thst issue see #293

[N-Montana]

Okay that's no problem, we'll make do without for now and try it with the new update. Thanks again for trying help in the meantime!