v11 - Utmstack Base URL is invalid if it contains a number

[uj]

Acknowledgements

• I have searched (https://github.com/utmstack/UTMStack/issues) for past instances of this issue
• I have verified that my UTMStack version is up-to-date

Describe the bug

In the Application Settings, if your domain name contains a number, the applications says "Utmstack base url is invalid"

For example:
This works: https://utmstack.mydomain.com

This is invalid: https://utmstack.mydomain1.com

Domain names are allowed to contain numbers, so this seems like a bug.

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

Allow the utmstack base url to contain a number in the domain part

Current Behavior

utmstack base url does not allow numbers in the domain part.

Reproduction Steps

Put a number into the utmstack base url domain part.

Possible Solution

No response

Additional Information/Context

No response

UTMStack Version

v11

Operating System and version

Ubuntu 24 LTS

Hypervisor and Version | Server Vendor and Model

Proxmox

Browser and version

Google Chrome

[uj]

This is still broken. Numbers (and other non-alpha characters) are still not allowed in the base url with v11.1.8.

The error is "Utmstack base url is invalid"

For example, try putting this into the base url field:
https://something.my1domain.com
or
https://something.my-domain.com

In both of those cases, you will see that there is an error and you cannot save the settings.

[osmontero]

@mjabascal10 can you please review this?

[mjabascal10]

Hi @uj , thanks for following up and for sharing the examples.

We’ve tested the base URL validation again on our side using v11.1.8, including cases with numbers and hyphens (such as my1domain.com and my-domain.com), and so far we haven’t been able to reproduce the issue. Both formats are accepted during our tests.

One thing that may help us narrow this down is checking whether the input field might contain an extra space or invisible character at the end of the URL. We’ve seen this cause the validation to fail in some cases.

Could you please try entering the URL again and confirm that there are no trailing spaces or hidden characters before saving?

We’ll continue investigating, but this detail would help us move forward.