Veeam One Reporter website publish to internet

[dontok]

Greeting,

we have Veeam One Reporter server in private network , i would like to publish it over internet in certain domain name ex reporter.example.com.
is it possible to publish it over nat to internet ?

sorry for my english

Thank you
Regards

[HannesK]

Hello,
and welcome to the forums.

Veeam ONE web client / reporter is a web application that runs on Microsoft IIS webserver. Like any other webserver I know, it can be published to the internet over NAT.



Best regards,
Hannes

[wishr]

Hi Ridwan,

Slight correction. The web server itself is a part of VONE server, while IIS is a part of the Web Services component that can be installed independently. We have not tested it with NAT, but I do not see any reasons why such configuration should not work. Our components are built on top of Microsoft libraries which are compatible with common networking technologies such as NAT is.

Thanks

[dontok]

thank you for replies

we tried to publish it to internet



but when we try to generate report / click preview in saved report



it brings to local address /url



i dont know much about iis, if you had link / guide to publish iis website to internet over nat, would be greate.

thank you.

[HannesK]

that looks like a DNS issue... tbsvmone.int[...]cloud.id doesn't resolve. So I assume fixing the DNS entry should work.

[dontok]

yes that my local hostname, but when published to internet we change to certain domain name



i found this settings in registry



i changed it from local hostname (ex svr01.mycorp.id) to my domain name (ex myvone.website.com) and remove the port (1239), it doesnt work.

it's a way to remove port on veeam one configuration.

thank you

[HannesK]

depending on the amount of machines we are talking about, I would probably just "fix" it in the hosts file. As .id is an official top level domain, also registering the domain should work (I would test with hosts file first).

For IIS settings: I did not change anything and it seems to work fine for me. reports are working

For the registry setting: I changed the hostname / domain to a domain that I own and kept the port. Looks like reporting works fine. I can create reports with preview.

I run my setup without NAT, but HTTPS must work with NAT.

[nikolaj]

Hi Ridwan,

Changing the URI in the registry just won't cut it in terms of name resolution.
You need to configure some sort of port forwarding/binding on the webserver (i.e. IIS) or on the network level.

Look at this thread on ServerFault for instance, or just google "IIS port forwarding NAT" in order to get a general idea.

Thanks.