Closed lonesomewalker closed 1 year ago
After creating a fake port which is not port 80, this works.
Additionally: The server-hostname cannot be used as customer-domain. Well... this is somewhat... annoying :-)
So the issue is that you want SSL only domains because having a different port than 80 is possible of course.
The server-hostname cannot be used as customer-domain.
Well, you can use e.g. "froxlor.domain.tld" for froxlor and still assign "domain.tld" for a customer. Assigning the same domain definitely makes no sense ..
Well... It makes sense in case of different ports... ;-) You have kinda unlimited possibilities for Apache/nginx as a proxy. So, yes, it would be nice to have domains which are SSL only, running on a different port. And yes, i know, this is an edge-case :D But i wanted to run an additional service on the hostname with a different port. (let me guess, easier done with a seperate config file for the webserver...)
So we have two things here:
1) The possibility to have ssl-only domains (this could be done, but it will take some time as this requires a lot of rework)
2) Having a separate service run on froxlor-hostname:[some-other-port]
The latter can easily achieved by e.g. specifying a proxypass directive for a specific folder or similar in the ip/port special-settings config:
Let's assume you have some service running on port 8080 and you want it to be accessible using the froxlor-hostname e.g. via https://froxlor.mydomain.tld/special-service
ProxyPreserveHost on
ProxyPass "/special-service" "http://localhost:8080"
ProxyPassReverse "/special-service" "http://locahost:8080"
In case you explicitly want the service to be accessible via http://froxlor.mydomain.tld:8080
you would need to create your own/custom virtual-host configuration as froxlor itself would only let it point to froxlor itself (in case of froxlor-hostname) or the customer-homedirectory (in case of customerdomain) and would even lead to the issue that your webserver wont't be able to start/restart because the port 8080 is already in use by the corresponding service hence it wont be able to listen on it
Okay, then i will use the typical approach: separate config file. Good that froxlor allows this to the server admins :-)
Describe the bug A domain should be able to setup WITHOUT port 80.
System information
To Reproduce Steps to reproduce the behavior:
Expected behavior It should be independent from port 80 to register a new domain in the system. Apache does not care :-)