Difficulty in Running OpenRemote using GitHub source code

Hi Guys,
I am facing problem to run OpenRemote. Before doing the customization, we are planning to run the OpenRemote using the source code.
Following steps has been followed:
Step 1:
We have downloaded the code form GitHub using the link.
GitHub - openremote/openremote: 100% open-source IoT Platform - Integrate your devices, create rules, and analyse and visualise your data

Step 2:
Preparing-the-environment

Step 3:
Installing using Dockers

Step 4:
Setup IDE

After following all these steps, we are getting following screen instead of login page:

Questions / Clarification:

  1. Why are we getting the blank page?
  2. Are we missing any components to add?
  3. Do we need to follow any other method?

Thank You

Hi,
Post docker-compose here

Hi Apurba,
The Docker compose file
docker-compose yml.txt (2.4 KB)

hi vicky
you mention localhost:9000 but in yml file where you mention this port

try to run localhost only in your browser otherwise change port no in yml file

Hi Apurba,
I changed port no but still it’s not working


is this correct. how i change port no 80:80 to 9000:9000

Hi,
go docker directory and run command
first----docker-compose pull

second ----- ```
docker-compose -p openremote up

then go to your browser and type localhost:9090

Hi,
Got the Error which run “docker-compose pull command”

Hi!

It seems like you are misconfusing the proxy / ports assignment here.
We have 2 different profiles, as mentioned in the Setting up an IDE documentation:

  • Without SSL, hosted on http://localhost:9000/manager/
  • With SSL, hosted on https://localhost/manager/

Be aware that those setups do not run the manager (Backend and UI), only the dependencies.
This should be ran within your IDE.

.
If you’re doing local development work, hosting without SSL and proxy is the plug-and-play option. Otherwise you need to add a few environment variables as mentioned in the docs.

No need to edit the ports in the docker-compose file btw, just keep the original one.
Would only make it more tough to solve :wink:

Because what is your use case exactly? This would help for providing the correct advice.
.


Regarding that last docker-compose pull issue; try restarting your Docker service / system.
If that does not work, check your network connectivity.

replace below code with yml file

OpenRemote v3

Profile that runs the stack by default on https://localhost using a self-signed SSL certificate,

but optionally on https://$OR_HOSTNAME with an auto generated SSL certificate from Letsencrypt.

It is configured to use the AWS logging driver.

version: ‘2.4’

volumes:
proxy-data:
temp-data:
postgresql-data:

btmesh-data:

services:

proxy:
image: openremote/proxy:${PROXY_VERSION:-latest}
restart: always
depends_on:
manager:
condition: service_healthy
ports:
- “80:80”
- “${OR_SSL_PORT:-443}:443”
- “8883:8883”
volumes:
- proxy-data:/deployment
environment:
LE_EMAIL: ${OR_EMAIL_ADMIN:-}
DOMAINNAME: ${OR_HOSTNAME:-localhost}
DOMAINNAMES: ${OR_ADDITIONAL_HOSTNAMES:-}
# USE A CUSTOM PROXY CONFIG - COPY FROM https://raw.githubusercontent.com/openremote/proxy/main/haproxy.cfg
#HAPROXY_CONFIG: ‘/data/proxy/haproxy.cfg’

postgresql:
restart: always
image: openremote/postgresql:${POSTGRESQL_VERSION:-latest}
volumes:
- postgresql-data:/var/lib/postgresql/data
- temp-data:/tmp

keycloak:
restart: always
image: openremote/keycloak:${KEYCLOAK_VERSION:-latest}
depends_on:
postgresql:
condition: service_healthy
volumes:
- ./deployment:/deployment
environment:
KEYCLOAK_ADMIN_PASSWORD: ${OR_ADMIN_PASSWORD:-secret}
KC_HOSTNAME: ${OR_HOSTNAME:-localhost}
KC_HOSTNAME_PORT: ${OR_SSL_PORT:–1}

manager:

privileged: true

restart: always
image: openremote/manager:${MANAGER_VERSION:-latest}
depends_on:
  keycloak:
    condition: service_healthy
environment:
  OR_SETUP_TYPE:
  OR_ADMIN_PASSWORD:
  OR_SETUP_RUN_ON_RESTART:
  OR_EMAIL_HOST:
  OR_EMAIL_USER:
  OR_EMAIL_PASSWORD:
  OR_EMAIL_X_HEADERS:
  OR_EMAIL_FROM:
  OR_EMAIL_ADMIN:
  OR_HOSTNAME: ${OR_HOSTNAME:-localhost}
  OR_ADDITIONAL_HOSTNAMES: ${OR_ADDITIONAL_HOSTNAMES:-}
  OR_SSL_PORT: ${OR_SSL_PORT:--1}
  OR_DEV_MODE: ${OR_DEV_MODE:-false}

  # The following variables will configure the demo
  OR_FORECAST_SOLAR_API_KEY:
  OR_OPEN_WEATHER_API_APP_ID:
  OR_SETUP_IMPORT_DEMO_AGENT_KNX:
  OR_SETUP_IMPORT_DEMO_AGENT_VELBUS:
volumes:
  - temp-data:/tmp

- /var/run/dbus:/var/run/dbus

# Bluetooth mesh volume

- btmesh-data:/btmesh

devices:

- /dev/ttyACM0:/dev/ttyS0

then run the command and post pic here

1 Like

Hi Martine,
Our use case is simple :
We want to do development environment setup. Before doing any modification we want to understand how to run and Configure OpenRemote using the source code.

Great! Well then the steps provided in the docs, and the ones I mentioned should work.
I would recommend running without proxy (dev-testing profile) to prevent hassle, and then following the steps in the ‘Setting up your IDE’ documentation. After that localhost:9000/manager/ should work.

You were already up and running, except the proxy was making life more difficult in your case. :grin:

Hi Martin, @apurba
I follow the above steps and got Sign in page after sinIn get “The site can’t provide a secure connection” on given URL “https://localhost:9000/auth/realms/master/login-actions/authenticate?session_code=sSHaCXhyKJTkcfKSbVNNaAUqXzXiPPU6vlEQ9wKul3o&execution=f1be5478-51ba-46d1-9228-96d7c7cb42b5&client_id=openremote&tab_id=XBYccLHRZHQ


Have any idea why this is showing

Hi,
you need to generate ssl certificate through proxy under “deployment”

Or replace domain name in place of localhost
U can buy domain or use freedns

In yml file
OR_HOSTNAME: ${OR_HOSTNAME:-localhost}

Hi @martin.peeters , @Rich @apurba @Don
I want to run as unsecure. so I don’t think SSL will need for this.

vicky

No you don’t need any extra configuration for this.
The screenshots you sent still use SSL; make sure you deleted all environment variables that use this.

All the issues you’ve mentioned until now are SSL related, while it doesn’t seem you want that.
So, try following the documentation from scratch, step by step, without SSL or the proxy, since that should not give any errors.

1 Like