Skidamek
Proxy servers / anti ddos may block AutoModpack
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
- Attempt to set automodpack to use a server domain
- 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
- [X] I have verified that the issue persists in the latest version of the mod.
- [X] I have searched the existing issues and confirmed that this is not a duplicate.
Do you use cloudflare dns proxy option? I recently got report that this somehow breaks automodpack host.
if thats the case please try latest dev build artifact its untested may not work but i changed slightly server host handling
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!
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?
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.
Okay just wanted to make sure, it does just fail with the same error even when the IP is left blank.
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
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!
Annoyingly we're currently in the process of switching to a new modpack and are having a few troubles getting things working properly, once it's up I'll test it!
Sorry about the delay, just tried with beta 22 on Neoforge 1.21.1 (ATM10) and it doesn't seem able to connect with the domain. I tried giving it a dedicated port to test but it just gives the same error as before.
If I tell it to use the actual IP rather than the domain it does work on connecting using the domain, which is a viable workaround but does potentially risk the IP - thus the domain.
If its not fixed with beta 25, your hosting has to change how they do the port forwarding or just find a different host, i can't do anything about