Openremote installation - ubuntu 24.04

Hello,

i have a Hetzner host with several VMs running.
For openremote i created a new ubuntu 24.04 machine.

For installation of openremote i try this manual:
Ubuntu Server Openremote Tutorial

First step:

sudo apt install default-jdk nodejs docker.io git
sudo apt-get install build-essential
curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

Then:

sudo mkdir -p /opt/openremote
cd /opt/openremote
sudo git clone https://github.com/openremote/openremote.git
cd openremote

Next should be this - which failed for me:

sudo make all

I leaved this step and went directly to:

sudo docker-compose up

This steps works without the make command before. Now the docker containers are running.

My question:

Are the setup steps above correct - do i leave something?

Will the make part cause problems?

Additional:
Now i can type my ip of the VM in browser and openremote opens.

But i cant login open remote says ā€œsorryā€
Invalid parameter: redirect_uri

Openremote should run without any dns or ssl. Only with my internal IP.
I have an nginx reverse proxy over all vms. This will keep the tricks for ssl.

Pls help. thx

Good morning @chris_haas ,

That guide seems to be quite old, and is about an older platform version of OpenRemote.

You can find the official documentation for installing OpenRemote here. It simply uses Docker’s Compose to start the OpenRemote platform.

Best of luck!

Panos

Thx for your reply.

I tested the second mentioned way from you:

  1. wget https://raw.githubusercontent.com/openremote/openremote/master/docker-compose.yml
  2. docker-compose pull
  3. OR_HOSTNAME=172.18.1.36 OR_SSL_PORT=8443 docker-compose -p openremote up -d

Not possible to login by 172.18.1.36 by browser. (blank page, error)

Then i tried again the old way:

  1. git clone the repository
  2. within the cloned directoy
  3. OR_HOSTNAME=172.18.1.36 OR_SSL_PORT=8443 docker-compose -p openremote up -d

does not work.

Than i try to:
sudo docker-compose up

Now i got the error:
Invalid parameter: redirect_uri
But i can see the openremote logo.

What do i miss here?

Thx

Hi @chris_haas,

When you don’t specify the OR_HOSTNAME variable before the docker-compose command you will get the redirect_uri error.
Can you try it again without the OR_SSL_PORT variable, like so:

OR_HOSTNAME=172.18.1.36 docker-compose -p openremote up -d

Make sure you execute this command in the directory where the docker-compose file is located

1 Like

that was the hint. thx

1 Like

I need some extra hint - now i want to use a fqdn with my existing nginx proxy (reverse proxy).

Note - My virtual machine with openremote works remote on hetzner without any problems. In the same netzwork i can open openremote and modify in 172.18.1.36

I have several virtual machines, and my reverse proxy settings redirects all domain traffic to their machines.

What worked so far:

OR_HOSTNAME=172.18.1.36 docker-compose -p openremote up -d

Normaly all the ssl stuff is done by nginx. And nginx redirects to openremote. Therefore i tried:

OR_HOSTNAME=openremote:fqdn.at docker-compose -p openremote up -d

Now i can browse to openremote:fqdn.at. But with some errors.

Erros:

  • I can login, but on assets tab there are problems in loading content. See attached picture.

This is my proxy settings:


server {
        listen 0.0.0.0:80;
        server_name openremote.xxx.at;

        location / {
                proxy_pass http://172.18.1.36;

                proxy_read_timeout 300s;

                # proxy header
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        }
}

server {
        listen 8443 ssl;
        server_name openremote.itc-haas.at;
        include snippets/ssl-params.conf;

    ssl_certificate /etc/letsencrypt/live/openremote.xxx.at/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/openremote.xxx.at/privkey.pem; # managed by Certbot

        # self signed
        # ssl_certificate /etc/ssl/certs/nginx-selfsigned.crt;
        # ssl_certificate_key /etc/ssl/private/nginx-selfsigned.key;

        location / {
                proxy_pass https://172.18.1.36;

                proxy_read_timeout 300s;

                # proxy header
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "Upgrade";
                proxy_set_header X-Forwarded-Ssl on;
        }
}

thx for help

Nope, again, also this link mentioned above after OpenRemote.
Al these commands ends with error, Git> not found no matter if i do it on a NUC, but also On my Qnap with Ubuntu See here:


I’ve already seen and followed about 30 different links on the forum, but none of them show the complete installation from Linux to Openremote. They always redirect you to a different page where you repeatedly encounter an error or ā€œcommand not found.ā€ And it has nothing to do with the hardware itself. I initially assumed I was using a NUC, but because everything kept crashing, I switched to my QNAP and installed Ubuntu there, and the same thing happened again. (The QNAP also uses twice the power of the NUC during a Docker installation, a whopping 12 watts more.) The only remaining option is using a Raspberry Pi, but that’s nowhere to be found on the Openremote page.
Is there even a complete installation manual anywhere that doesn’t constantly redirect to other (non-functioning) pages?

you run update command and install command without && this does not work.

Try my manual above line by line and it should work.

I have an exisiting installation running but only without domain name.

Hmm, what do you mean with && are they parameters?

i tried this:
Warning: Failed to open the file /usr/local/bin/docker-compose: Permission
Warning: denied
0 72.0M 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
curl: (23) Failure writing output to destination
chmod: cannot access ā€˜/usr/local/bin/docker-compose’: No such file or directory
bonestaak@ubuntu-2404:/opt/openremote$ sudo mkdir -p /opt/openremote
bonestaak@ubuntu-2404:/opt/openremote$ cd /opt/openremote
bonestaak@ubuntu-2404:/opt/openremote$ sudo git clone GitHub - openremote/openremote: 100% open-source IoT Platform - Integrate your devices, create rules, and analyse and visualise your data
Cloning into ā€˜openremote’…
remote: Enumerating objects: 131367, done.
remote: Counting objects: 100% (1749/1749), done.
remote: Compressing objects: 100% (890/890), done.
remote: Total 131367 (delta 1265), reused 922 (delta 801), pack-reused 129618 (from 3)
Receiving objects: 100% (131367/131367), 283.99 MiB | 29.41 MiB/s, done.
Resolving deltas: 100% (67302/67302), done.
bonestaak@ubuntu-2404:/opt/openremote$ cd /openremote
bash: cd: /openremote: No such file or directory
bonestaak@ubuntu-2404:/opt/openremote$ cd openremote
bonestaak@ubuntu-2404:/opt/openremote/openremote$ sudo docker-compose up
sudo: docker-compose: command not found
bonestaak@ubuntu-2404:/opt/openremote/openremote$ sudo make all
make: *** No rule to make target ā€˜all’. Stop.
bonestaak@ubuntu-2404:/opt/openremote/openremote$ OR_HOSTNAME=192.168.0.167 OR_SSL_Port=8443 docker-compose -p openremote up -d
bash: docker-compose: command not found

I think directories are different on Qnap docker and there is no path as most of the commands are not found

Good afternoon @bonestaak ,

As you can see in our quick-start documentation, which I’ve referred you to before, the prerequisites for running OpenRemote locally are quite clear: Docker desktop (version 18+), and the OpenRemote docker-compose file. There are no other requirements, other than basic Linux and command line knowledge.

You only need to download Docker, which includes docker compose, and run the commands you can see in the quick start documentation.

The only method of running OpenRemote locally (without recompiling the code) is the one I mentioned and can be found in our official documentation. You have tried to run versions of OpenRemote going back to 2013!!!

Unfortunately, there is no easier way of running OpenRemote, such as using apt-get install, qnap, etc. You will need to download Docker and run OpenRemote using that.

If you are not comfortable with using the Linux shell, there are various AI models like ChatGPT that are more than capable of helping you. As of right now, you are just downloading files and running commands you find on forums and websites that not only are wrong, but are also insecure and could pose a security threat for your computer.

If there is an issue that the LLM of your choice cannot solve, you can let us know in this forum. You can give it our quick-start documentation so that it can help you out.

Best of luck!

All right, i start again with the Quick start documentation, and i will start again with the NUC, The Quick start doc is starting with Docker Desktop, but of course i must first have some Linux (there was Ubuntu on the NUC but it works terrific slow so i think its the wrong one, so which image to install on the NUC?

@bonestaak , Ubuntu 24.04.2 LTS would be okay.

For this moment i have used the old Ubuntu (i think its 22) What was already on the NUC.
i tried ```
docker-compose pull
docker-compose -p openremote up
ls > bobwalberg/Downloads thats whats going wrong, not /download but Downloads

Nope, permission denied so i tried. sudo before and yes pull is downloading
So also sudo docker-compose

Now i got (with localhost on my NUC) Openremote after aboud 10 minutes (yes the linux on my NUC is slow.

@bonestaak I’m sure that if you paste the entirety of your console logs to an LLM it’ll be eager to help you. It seems that you are probably storing the docker compose file somewhere wrong.

HI, do you have also information for me running behind proxy with domain?

I already have overviewed your quick start guide. But not sure which information should be useful for my problem.

As I said remote with IP it works. With fqdn docker compose startet it also works but I have errors in Assets. As shown in the picture above.

thx