dynamic dns issue

How did you resolve this on UTM? 

What do you mean?

You wrote, you are a UTM user. How did you do this on UTM, so we can map the same construct on SFOS. 

Oh, OK, I see..

Unfortunately the UTM has now been replaced by the XG.

But the way it was working was the way I described above.

In webserver protection section you were creating the virtual server. It had the dyndns hostname, the listening interface and the port 80. Then you had the "real" webserver. You were defining the internal IP, and the port (8086) and you were matching it with the previously created virtual one. I will try to login to the UTM and make screenshots

OK, so here we go.

The first thing you were doing is setting the real webserver. For motioneye, see below the settings:

Then you were creating the virtual webserver and you were selecting the real one created before. The logic is basically the same in XG

And that was it.

And for the second Webserver? 

Sorry, thought that one example will be enough.. 

Please see below the other two:

Here is Pyload (will be replaced with emby in XG)

The Real Webserver part

And this is the Virtual webserver part

And finally the "root" one which is on port 80

Real:

Virtual

The way it was working was this:

When I hit from the browser http://srv.ddns.net I was getting to port 80 of the InsomniaWebSRV 

When I hit from the browser https://srv.ddns.net:4444 I was getting to sophos UTM webadmin page

When I hit from the browser https://srv.ddns.net I was getting to sophos UTM portal

When I hit from the browser http://motion.ddns.net I was getting to the motioneye login page which was hosted on port 8096 of InsomniaWebSRV 

When I hit from the browser http://pyload.ddns.net I was getting to the pyload login page which was hosted on port 8000 of InsomniaWebSRV 

As I mentioned already, all dyndns names should lead to the same server, just different ports.

Just to test, I tried something else. I created a different web server which leads to an openspeedtest docker on my synology nas

So the webserver is a completely different ip address.

Entering the DDNS hostname again redirected me to the first webserver again on port 80, which is rather strange

So a question, just so that it is written here... In network -->DDNS I have entered all 3 of those dyndns names..

Do they need to be removed from there? And only add them in the WAF settings?

(which does not make much sense, of course, since the needed authentication for dyndns only exists in Network-->Dynamic DNS tab)

As I mentioned already, all dyndns names should lead to the same server, just different ports.

Just to test, I tried something else. I created a different web server which leads to an openspeedtest docker on my synology nas

So the webserver is a completely different ip address.

Entering the DDNS hostname again redirected me to the first webserver again on port 80, which is rather strange

So a question, just so that it is written here... In network -->DDNS I have entered all 3 of those dyndns names..

Do they need to be removed from there? And only add them in the WAF settings?

(which does not make much sense, of course, since the needed authentication for dyndns only exists in Network-->Dynamic DNS tab)

Ok, update post just to say that I did remove them and it was still redirecting to port 80 of the server, but since dns is involved here, my guess is that when they are removed and noip gets no updates they will simply redirect to nowhere...

Anyway, is there anyone with a scenario like this who can confirm that it is working? 

Does anyone need any additional info about my setup in order to help find out what the issue is?

thanks! 

Can someone please offer some insight?

Should I try a factory reset or something? Setting all the stuff I have once more it will be quite a task, but I really don't know what else to try. This specific task should be the simplest one. But it is not working for me..

I am currently thinking, this is not possible in SFOS. Based on the integration of the services, the web app will be hosted on IP base, not SNI. 

Can you please explain what you mean?

The UTM separate the request (FQDN) based on SNI. Server Name Identification. It looks like, SFOS cannot do this. 

So how can it be used as a reverse proxy? Only with path specific routing? 

You tested several ways. And as your results, it seems not to work based on FQDNs. Therefore you cannot do your setup. 

I see what you mean.. But the thing is that it is accepting FQDNs in the firewall rule and looking at the documentation I cannot understand that this is not supported..

XG was supposed to be one step up in the reverse proxy rule compared to UTM. Is it really one step back? What I mean is, are we sure that there is not something wrong in my software setup?

Do you have some inside info perhaps? Is this something that is going to be fixed in a later release?

Thanks a lot man!

EDIT: Do you think I should create a new post describing exactly this and asking for verification that it can actually be done?

It could potentially work, if you define the domain per WAF Rule. 

So this should work, and separate the Domains like UTM did. 

Thanks for taking time trying to help me !

I think I have already tried this but it does not hurt to give it another try, I guess

I will post back