When surfing 0.0.0.0:8001, message "Invalid host header" appears. Is this supposed to happen? What's next? about server HOT 3 OPEN

I found out what the issue was. I had to add my local IP as allowed host in etebase-server.ini besides my domain name and it worked. But still, what should I do next?

from server.

I've managed to bring up the server running. It runs perfectly.
Now, another question arose. My service is available at mydomain.com:443. Is it possible to run HTTPS service without occupying port 443? I would like to host various instances with the same domain mydomain.com, but different instances would be available via different ports.
When I get SSL certificate for mydomain.com, do I need to run certbot for verey instance which uses this domain but different port?
Could someone please show me which settings should I change for etebase to be accessible from different port than 443?

from server.

@ManmadeStarch yes it's possible to use another port than 443.
If you use the same domain name, the same certificate should be possible to use.

I can try to to show you how to do this, but it's not really clear to me what is your final working configuration.

from server.