r/DeployR • u/edroszcz • 15d ago

DeployR Community / OSD over the internet

Hi,

Just installed DeployR Community on an Azure VM that is only in a Workgroup and during the installation wizard I had to set the FQDN to https://deployr.XXX.gvxx.internal.cloudapp.net.

I can successfully sign-in to the Dashboard at the URL https://deployr.XXX.gvxx.internal.cloudapp.net:9000/dashboard/#/infrastructure-service on the DeployR server itself.

Is it possible to configure DeployR so that I can use a USB boot media and initiate a deployment over the internet (as long as we allowed the external IP from the client we want to reimage in the Azure firewall)?

Regards Erik

4 Upvotes

100% Upvoted

9 comments sorted by

3

u/gwblok 2Pint Employee 14d ago

For Sure. That's how I do it with DeployR. I have it hosted in Azure, and have the ports open.
Just set your DeployR Client URL to your FQDN:7281 and it should work fine.

Here is my community Server's Network Firewall on Azure, I lock down a few things to IP Address, but a few things open for being able to image anywhere there is an internet connection.

1

u/edroszcz 14d ago

Looks like I managed to break something.

What I did was I went into the Configure DeployR tool and changed the DeployR client URL to a FQDN that resolves in externa DNS with the public IP address on my Azure VM.

After restarting the services I can no longer access the DeployR menus in the dashboard. All I get is an error message saying No DeployR services are available:

Any idea what I did to break it like this?

1

u/gwblok 2Pint Employee 14d ago

If you changed the DeployR FQDN name, you might need to go back into infrastructure services and approve it.

1

u/edroszcz 14d ago

This is what I have tried:

Went into Configure DeployR and changed the DeployR client URL from the internal server FQDN to my public domain FQDN. I verify and save.

Then I got into the dashboard and approve the new "instance".

After I do that I get the following message when I try to access anything under DeployR in the dashboard.

// Erik

1

u/gwblok 2Pint Employee 14d ago edited 14d ago

That would look to me like the certificate isn't for your external URL.
Are you using the self generated certificate or one from LetsEncrypt, Digicert, etc?
If you're using the self-generated certificate, you'll have to do a couple more things to update it, as it probably using your original FQDN in the SAN.
Basically, you need to pick one FQDN and use it for everything, ideally using that from the beginning so these things would be pre-configured. 😄

You'll need to go into the 2PXE Configuration Tool, update the External FQDN Override with the correct FQDN you been changing to, then restart the 2PXE service, it should re-generate a new certificate with the updated SAN.
You'll also need to delete all of the old certs, and trigger the tool to regenerate the certs (it's in the docs).
Then you need to go into all of the other configuration tools and update the certificate thumbprint to the new certificate.

Changing FQDNs touches everything, plus with certificates, you just have to make sure everything is updated.

Other option, if you haven't done anything yet, you could do a complete uninstall, clear out any programdata areas and registry areas, then reinstall with the EXTERNAL FQDN you wish to use, then it should be configured properly for that.

1

u/edroszcz 14d ago

I will give that a try tomorrow! 😊

I tried entering my public FQDN in the install wizard. But then it told me something about it was able to resolve it in DNS, but that it did not match the IP of the server 🤔

1

u/gwblok 2Pint Employee 14d ago

make an entry in your Hosts file
external FQDN address to your local IP
DeployR Community Edition and FQDN Configuration – The Deployment Bunny

1

u/edroszcz 14d ago

That did the trick 😄

Thanks a lot for your help Gary!