1. What is the issue? Please be detailed.
I have a self hosted ODK Central Server running on a custom port 8443. I recently upgrade to v2025.1.0-1-g282d220. After the upgrade, it seems like with enketo client, the edit link of submissions,
https://my-domain:8443/v1/projects/projectid/forms/formID/submissions/uuid:2dc61ee8-1853-41ce-a1c3-86e9033cbee5/edit
is not well redirected. It's redirected to https://my-domain/f/6MgMqUBRoID20kP7Xk46q5DARBA3BJM/edit?instance_id=uuid:2dc61ee8-1853-41ce-a1c3-86e9033cbee5&return_url=https://my-domain:8443/projects/projectid/forms/formID/submissions/uuid:2dc61ee8-1853-41ce-a1c3-86e9033cbee5
with no port number.
When i add the port number it works. But if i click on the edit pencil link it redirects to the wrong address (without port number)
Sorry to hear the update has negatively impacted you! Are you exposing Central on port 8443 because you have another service on the host? For another reason?
In general, we expect Central to be running at default ports. That could entail, for example, serving it from a subdomain. We'll make sure that's explicitly documented.
Did you have to make any other changes to get your configuration to work? For example to the Enketo configuration? We will likely patch this to maintain backwards compatibility but are trying to decide whether to explicitly documented as unsupported moving forwards.
Looking more into this, I now remember that we expose HTTPS_PORT in .env which certainly suggests we support it! I'm still curious to understand more about your specific needs.
If anyone else uses a custom port, I'd also love to hear more about why and what your experience with it has been overall.
I vaguely recall running into problems with Enketo's (absolute) URL construction too, on my dev setup when I was working on the Enketo/Webforms juggle. 
This is exactly what I am facing here. The URL is not getting the ID of the form then it creates a wrong URL which then returns this error "No Form found with this URL, please double check.". Have you found a work around with this?
Upgrade to Central v2025.1.2. It has a fix.