Deploying on Linux

YogiYang

Hello,

I am not able to understand step #4.

Add connection details to an empty, UTF8 encoded PostgreSQL database to config.json. The database user must have full permissions for the chosen database.

What have I to set in the config file?

TIA

Yogi Yang

lsw-fabian

YogiYang You have to install Postgres at first - after that, you have to create new user + database and enter the information (database, user, password) to REI3's config file.

Check this link to get an easy tutorial on how to set up postgres on ubuntu

YogiYang

lsw-fabian

Thanks it is working!

I managed to extract the files.

TIA

Yogi Yang

YogiYang

Hello,

lsw-fabian Check this link to get an easy tutorial on how to set up postgres on ubuntu

Can you please update the documentation and put this link there?

TIA

Yogi Yang

YogiYang

Hello,

I have managed to install PostgreSQL and start R3 as service.

Now how do I access it from my browser?

TIA
Yogi Yang

lsw-fabian

If R3 service is started, you should be able to reach your R3 instance via browser. Normally it should be https://localhost:443 on your first startup. (or use the port you configured in REI3's config file.)

If you want to connect via another pc you have to make sure that your firewall will allow the communication.

YogiYang

Hello,

When I point my browser to it.

This is what I am getting

TIA

Yogi Yang

lsw-fabian

Looks like you still have another service running on port 443.
Stop R3 service, set another port in the REI3 config file (e.g. 444) and restart the service.

YogiYang

Hello,

Setting the post to 444 seems to work but I am getting this in browser.

Is it necessary to setup SSL?

If Yes, then how to set it up?

TIA

Yogi Yang

lsw-fabian

Thats normal with a new REI3 instance - REI3 just provide a self signed ssl certificate. If needed, you have to create and implement your own ssl certificate - however, as long as this isn't an productive environment you can just ignore this warning.

holoc

Hi, I'm also trying to deploy REI3 on Linux alongside another service (Apache2) running on 443.
Both seem to work on the same port 443.
However, REI3 instance seems to run out of https://localhost/#/
Is there a way to change the # directory to something else?

gabriel

holoc
Welcome to the forum 🙂

Unfortunately, you generally cannot run two applications on the same port if they run on the same system.

You can setup a proxy to serve 2 web applications on the same port to the outside world - but if both applications run on the same system, they still require 2 ports facing the proxy server.

In REI3 you can simply change the port in the config.json file and then restart the service. Then there is no conflict.

The '#' in the URL is a placeholder used by the REI3 web application - this is required for the web application to run and cannot be changed.

Unfortunately you will need to use unique ports for each application running on the same system - there is no way around that.

holoc

Thanks gabriel !

I will just disable the Apache server for now since I'm not really using it.
Since we're talking about multiple web apps, say if I wanted to run 2 separate REI3 apps on ports 443 and 444.
Do I use a proxy server like Squid to redirect two different domains to each of the ports?

lsw-fabian

holoc Hi Holoc, you don't need a proxy to host multiple instances. Just change the port number in your instance's config.json file and enter it with the configured port number like https://instance:444.

gabriel

holoc
If you want to run multiple domains on the same system, you would classically use a proxy like Squid, yes. Running Squid on the same system, this could be your setup:

Squid would use port 443 so that all incoming traffic (any domain you have) talks to the default HTTPS port (443).
Any other web app (like apache or any number of REI3 instances) would need to use ports other than 443 (because Squid uses it already). So REI3 instance #1 could use 14500, REI3 instance #2 could use 14501, etc.

Just make sure that each REI3 instance has a SSL certificate for the correct domain and that Squid sends traffic for each specific domain to the correct REI3 instance (by sending it to the right port). This way you can have multiple domains all talking to port 443 (no ugly port numbers in your URL).

Another small thing: REI3 uses Websockets, so you should have a quick google on how to configure Squid so that clients are not constantly disconnected.

holoc

Thank you gabriel for clarifying the port setup. Also noted about the websockets usage.

dmarsamoya

someone help me, I already start the rei3 but when I run it to browser unable to connect

fmvalsera

dmarsamoya

Have you tried http://localhost:8080 in your browser?

What is the command you are executing?

dmarsamoya

I executing the systemctl start rei3 but still the same unable to connect that's my encounter problem

fmvalsera

Can you show here the systemd .service file? Also It could be helpful if you show us your config.json file with REI3 configuration.

On the other hand, rather than starting REI3 through systemd, maybe you can execute manually in command line "r3 -run -http" for testing.