OR_HOSTNAME=<own IP> blank manager screen 403 forbidden

I tried running openremote on my local machine which works fine. Now I want to be able to access the ui on my IP address, lets say 1.2.3.4. On a windows pc running Docker Desktop I checked out the custom project github (GitHub - openremote/custom-project: Template repo for creating an OpenRemote custom project) and followed the guide (Custom deployment | OpenRemote Documentation). I have had this working on localhost, so now I am running the following command inside the custom-project repo:
cmd /C “set OR_HOSTNAME=1.2.3.4 && docker compose up”

I can now reach the log in screen on 1.2.3.4 and use the same username and password as before, but after log in I get a blank screen. In the console I get a 403 forbidden from POST request to https://1.2.3.4/api/master/console/register

What is shown in the quick start guide works with the default docker compose profile in the main repo:

Hello. I have tried to start an OR instance with the OR_HOSTNAME parameter, and it generates a 403 error when the HTTP APIs are invoked ( /api/realm/* ) and when looking at the result of the request to the API in the browser’s developer tools, the error origin not allowed is returned.

I have checked the keycloack component in the openremote client ( weborigins and redirects urls and I have updated them to the OR_HOSTNAME url, by default it is https://localhost/*) but the error persists.

I have created a service user and a user with superadmin and the error persists.

I don’t know if the error is associated with the manager or with keycloack

Hi @lizzard40

Curious if you ever got this to work? I am trying a custom hostname (with an A record to a public IP in our DNS server) and ports 80, 443, 1883, 8883, and 8443 forwarded to the Windows (Docker Desktop) host’s private/internal IP.

I can get to the authentication page like you can, but the redirect winds up on a white screen. I can also get to KeyCloak just fine on fqdn.com - This website is for sale! - fqdn Resources and Information..

Also the SSL seems to be accepted in Safari but not Chrome, not that I mind but thought I’d mention in case it is relevant.

Hey folks,

Am I missing something obvious here? Alternatively is there a paid support option?

Seems like a major sticking point, or bug if one can’t set this up out of the box and have it work with a custom domain name.

Thanks

@martin.peeters is it possible this is a bug? Or is there somewhere else I should be asking this question?

Thanks!

Issues during the setup of a custom hostname are quite common here on the forum.
In most cases it’s a configuration issue, so this doesn’t necessarily sound like a bug to me.
There also seems nothing wrong with the details you provided.
But feel free to open up a new topic to discuss your issue :slight_smile:

Double checked the Quick Start guide in the documentation, and it works fine for me locally.

Yes, there is, contact @Pierre or @Don for details.