I am running a server with this modpack, and recently I decided to setup a subdomain and srv record since I like this pack and will be sticking with it, but it's impossible to connect! Clients are prompted with a resource pack prompt, yet there's no resource pack in the server (and the option in server.properties is set to false)!

It's also impossible to click anything, and upon disconnect clients are met with "Invalid Payload REGISTER!" Connecting by specifying the port works, but that defeats the purpose of the srv record. The other server (vanilla) I am running is perfectly connectable via its srv record. I am running the server via the itzg/minecraft-server Docker container, but the issue persists even when running the server directly

You are doing something wrong, I just setup the latest server, using the provided .sh file, set my A record to point to my dedis IP address and connected.

Maybe explain your records a bit more, first thoughts to me are firewall, docker port mappings, incorrect DNS records, and a few other things, like the docker you are using isn't an official docker image for this mod.

Honestly, if you want to use docker Id recommend editing the docker file and set it up to install the server when the docker is being setup using the official server files the devs have provided. Other then that, you have provided no real information of your issue, no logs, no records, nothing of use.

You are doing something wrong, I just setup the latest server, using the provided .sh file, set my A record to point to my dedis IP address and connected.

Highly unlikely. Also you said you're pointing to an IP address which I already mentioned works just fine. It's the srv record that the client is having issues with, which again I've mentioned my vanilla server has zero issues with. I know this modpack, like all good modpacks, include heavy client side customizations and I believe there may be an issue with one of those.

Maybe explain your records a bit more, first thoughts to me are firewall, docker port mappings, incorrect DNS records, and a few other things, like the docker you are using isn't an official docker image for this mod.

All port mappings are correct as again clients can connect via ip/domain:port. Also there is no official docker image for this mod as that'd be kinda silly.

I'd look up what a srv record is as they're extremely useful for people who run multiple Minecraft servers like me.

Honestly, if you want to use docker Id recommend editing the docker file and set it up to install the server when the docker is being setup using the official server files the devs have provided.

The container is using the official server files the devs have provided completely unmodified, literally dropped into the container's data directory. It's even using the included Forge installer even though I can specify that version to download. The container simply provides the container and Java (which the modpack doesn't include a Java build for obvious reasons).

Other then that, you have provided no real information of your issue, no logs, no records, nothing of use.

1. Logs aren't going to be too helpful as the server doesn't even acknowledge a connection

2. You don't need my actual srv record to diagnose the issue, you should know what a srv record is.

Look, I was just trying to help you out. I know very well what the SRV records are for. Without logs of some sort, it basically not possible to debug whats going on or why. I can try to recreate the issue, but like I said, I don't know how your system is working, is it linux, do you use bind for dns, you are not giving details besides common knowledge of minecraft and with what you have given, it will not be the most simple thing to diagnosis unless the issue is with a mod itself, and it will still be very hard to diagnosis without logs from somewhere like your DNS server, the dedi sys logs, something that is showing the connection attempt and failure and giving you a starting point to solve your issue.

What I can do is simple change my port, add the records and see if it happens on my side of things, but without some sort of log to dig into, you are going to have to try change stuff till it works or find some logs somewhere.

Stand by for my DNS to propagate.

Works just fine for me.

Registered brand new domain

Created my A records like first post claims

Pointed SRV record from domain.example to _minecraft._tcp.domain.example port 25566

Waited for DNS to properly propagate

ping domain.example

host -t srv _minecraft._tcp.domain.example and confirm the end point domain and port are correct

connect minecraft client via new domain, new port, new a records, new SRV records

????????

profit

Like I said, you must be doing something wrong but rather you lash out and claim your setup is correct and should work since you have one server working the same way.

Also, it WOULD really help to know what your records look like, I don't need to know what they are just how they are formed.

cobb@araura:~$ host -t SRV _minecraft._tcp.example.net
_minecraft._tcp.example.net has SRV record 0 0 25566 craft.example.net.

Explain your situation and maybe I can help you, until you explain more, I can't help you.

cobb@araura:~$ ping craft.example.net
PING craft.example.net (000.000.000.000) 56(84) bytes of data.
64 bytes from server1.sample.com (000.000.000.000): icmp_seq=1 ttl=57 time=84.3 ms
^C
--- craft.example.net ping statistics ---

You don't even need srv records if you're using Minecraft's default port.... Try it with a nonstandard port next time.

Again, it can't be on my end because my other server is perfectly functional also with a non-standard port and this isn't my first time setting up a container, I've been doing it since 1.7.10 was fresh.

i changed port to 25566, read my posts.

"It works for me must be you" doesn't constitute offering help.

I know some carriers just cannot process srvs properly. Ran into that when utilizing local providers VS big guys. From the sounds of it though you've had success before. I'm more concerned with the resource pack prompt. If it's not hitting the server on that port is there another local server running that it's hitting on the box? Perhaps a proxy is running and sending the request elsewhere on the node to a server requiring a resource pack prompt?

@NachtRaben There is another Minecraft server running, but it's on a different port and the srv record is pointing to the ATM7 server (I've double-checked in Cloudflare and in my gateway's config). Another data point is that my friends seem to be able to connect just fine so perhaps it is just an idiosyncrasy with my ISP. The server itself I am hosting locally on my homelab setup.

I would make a safe assumption that your ISP is causing issues with a DNS server override probably. You can try setting your computer to cloudflare DNS with 1.1.1.1, 1.0.0.1 and hope? but with my rural connections that didn't work for me. You might have better luck. If its in a home lab though and external works for friends I'd just connect directly and save the headache.

@NachtRaben For me it's not an issue, I can just connect locally like you mentioned, I was just testing external connections.