serwer supla na linux

lesny8 · Post Mon Dec 07, 2020 7:40 pm

Softów jest od groma na forum. Na pewno uda Ci się coś dopasować do posiadanego sprzętu.
Dużą popularnością w ostatnim czasie cieszy się GUI Generic ze względu na swoją uniwersalność.

ocean · Post Fri Dec 18, 2020 6:09 pm

my server

Code: Select all

Recreating supla-db ... done
Recreating supla-cloud ... done
Recreating supla-server ... done
SUPLA containers has been started.

docker ps

Code: Select all

CONTAINER ID        IMAGE                COMMAND                  CREATED              STATUS              PORTS                              NAMES
349661c0af1a        supla_supla-server   "/usr/bin/server-ent…"   About a minute ago   Up About a minute   0.0.0.0:2015-2016->2015-2016/tcp   supla-server
c79e2c2ffca0        supla_supla-cloud    "docker-php-entrypoi…"   About a minute ago   Up About a minute   80/tcp                             supla-cloud
5d26bc206a42        mariadb:10.3.27      "docker-entrypoint.s…"   About a minute ago   Up About a minute   3306/tcp                           supla-db

Code: Select all

root@arm-64:~/supla-docker# docker logs  supla-server
2020-12-18 17:52:02,384 CRIT Supervisor running as root (no user in config file)
2020-12-18 17:52:02,396 INFO supervisord started with pid 1
2020-12-18 17:52:03,404 INFO spawned: 'supla-scheduler' with pid 11
2020-12-18 17:52:03,414 INFO spawned: 'supla-server' with pid 12
INFO[1608313923.448625] Scheduler version 2.3.9
INFO[1608313923.451295] Started at Fri Dec 18 17:52:03 2020
INFO[1608313923.458548] Server version 2.3.27 [Protocol v13]
INFO[1608313923.461659] Started at Fri Dec 18 17:52:03 2020
ERR[1608313923.466644] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
INFO[1608313923.469468] Connecting to database ....
ERR[1608313923.474282] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
INFO[1608313923.474366] Connecting to database ....
2020-12-18 17:52:04,476 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-12-18 17:52:04,479 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
ERR[1608313924.479239] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313924.482095] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313925.482481] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313925.485901] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313926.485179] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313926.488658] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313927.487895] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313927.491658] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313928.491120] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313928.494830] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313929.493474] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313929.497491] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313930.496071] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313930.500790] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313931.498456] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313931.502975] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313932.501950] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313932.506584] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313933.504930] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313933.509497] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (111 "Connection refused")
ERR[1608313934.523777] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[1608313934.524293] The version of the database can not be determined!
ERR[1608313934.523774] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[1608313934.524244] The version of the database can not be determined!
2020-12-18 17:52:14,528 INFO exited: supla-scheduler (exit status 1; not expected)
2020-12-18 17:52:14,529 INFO exited: supla-server (exit status 1; not expected)
2020-12-18 17:52:14,535 INFO spawned: 'supla-scheduler' with pid 13
2020-12-18 17:52:14,542 INFO spawned: 'supla-server' with pid 14
INFO[1608313934.564304] Scheduler version 2.3.9
INFO[1608313934.564653] Started at Fri Dec 18 17:52:14 2020
ERR[1608313934.575282] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
INFO[1608313934.576611] Server version 2.3.27 [Protocol v13]
INFO[1608313934.577034] Started at Fri Dec 18 17:52:14 2020
ERR[1608313934.576035] The version of the database can not be determined!
2020-12-18 17:52:14,579 INFO exited: supla-scheduler (exit status 1; not expected)
ERR[1608313934.587505] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[1608313934.588065] The version of the database can not be determined!
2020-12-18 17:52:14,592 INFO exited: supla-server (exit status 1; not expected)
2020-12-18 17:52:15,602 INFO spawned: 'supla-scheduler' with pid 15
2020-12-18 17:52:15,614 INFO spawned: 'supla-server' with pid 16
INFO[1608313935.664071] Scheduler version 2.3.9
INFO[1608313935.664524] Started at Fri Dec 18 17:52:15 2020
INFO[1608313935.675469] Server version 2.3.27 [Protocol v13]
INFO[1608313935.675918] Started at Fri Dec 18 17:52:15 2020
ERR[1608313935.677384] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[1608313935.678231] The version of the database can not be determined!
2020-12-18 17:52:15,681 INFO exited: supla-scheduler (exit status 1; not expected)
ERR[1608313935.687790] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[1608313935.688347] The version of the database can not be determined!
2020-12-18 17:52:15,691 INFO exited: supla-server (exit status 1; not expected)
2020-12-18 17:52:17,703 INFO spawned: 'supla-scheduler' with pid 17
2020-12-18 17:52:17,715 INFO spawned: 'supla-server' with pid 18
INFO[1608313937.764095] Scheduler version 2.3.9
INFO[1608313937.764622] Started at Fri Dec 18 17:52:17 2020
ERR[1608313937.781485] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
INFO[1608313937.781763] Server version 2.3.27 [Protocol v13]
INFO[1608313937.782431] Started at Fri Dec 18 17:52:17 2020
ERR[1608313937.782541] The version of the database can not be determined!
2020-12-18 17:52:17,788 INFO exited: supla-scheduler (exit status 1; not expected)
ERR[1608313937.799730] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[1608313937.800620] The version of the database can not be determined!
2020-12-18 17:52:17,806 INFO exited: supla-server (exit status 1; not expected)
2020-12-18 17:52:20,817 INFO spawned: 'supla-scheduler' with pid 19
2020-12-18 17:52:20,824 INFO spawned: 'supla-server' with pid 20
INFO[1608313940.849025] Scheduler version 2.3.9
INFO[1608313940.849419] Started at Fri Dec 18 17:52:20 2020
INFO[1608313940.858262] Server version 2.3.27 [Protocol v13]
INFO[1608313940.858663] Started at Fri Dec 18 17:52:20 2020
ERR[1608313940.868034] Incorrect database version! Expected: 20200911231401
2020-12-18 17:52:20,873 INFO exited: supla-scheduler (exit status 1; not expected)
ERR[1608313940.874473] Incorrect database version! Expected: 20200911231401
2020-12-18 17:52:20,875 INFO gave up: supla-scheduler entered FATAL state, too many start retries too quickly
2020-12-18 17:52:20,878 INFO exited: supla-server (exit status 1; not expected)
2020-12-18 17:52:21,880 INFO gave up: supla-server entered FATAL state, too many start retries too quickly

lesny8 · Post Fri Dec 18, 2020 9:59 pm

ocean wrote: Fri Dec 18, 2020 6:09 pm
Code: Select all
...
ERR[1608313940.874473] Incorrect database version! Expected: 20200911231401
...

ocean · Post Sat Dec 19, 2020 12:37 am

Can you help me fix the error

lesny8 · Post Sat Dec 19, 2020 10:03 am

Code: Select all

docker logs supla-cloud
docker logs supla-db

ocean · Post Sat Dec 19, 2020 1:09 pm

log here, it very long
https://www.mediafire.com/file/i4lz0y19 ... s.txt/file

lesny8 · Post Sat Dec 19, 2020 3:45 pm

Everything's look good. Database was created, every migration was done and it is in correct version. Restart dockers and check login to Cloud.

Code: Select all

./supla-docker/supla.sh restart

ocean · Post Sat Dec 19, 2020 4:49 pm

Code: Select all

root@arm-64:~# docker logs --since=5m supla-cloud
 [OK] Cache for the "prod" environment (debug=false) was successfully warmed.

User [email protected] already exists.
2020-12-19 16:42:53,116 CRIT Supervisor running as root (no user in config file)
2020-12-19 16:42:53,134 INFO supervisord started with pid 1
2020-12-19 16:42:54,141 INFO spawned: 'apache' with pid 51
2020-12-19 16:42:54,148 INFO spawned: 'cron' with pid 52
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message
[Sat Dec 19 16:42:54.872173 2020] [ssl:warn] [pid 51] AH01906: 172.18.0.3:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Sat Dec 19 16:42:54.872569 2020] [ssl:warn] [pid 51] AH01909: 172.18.0.3:443:0 server certificate does NOT include an ID which matches the server name
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message
2020-12-19 16:42:55,141 INFO success: apache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
[Sat Dec 19 16:42:55.432162 2020] [ssl:warn] [pid 51] AH01906: 172.18.0.3:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Sat Dec 19 16:42:55.432317 2020] [ssl:warn] [pid 51] AH01909: 172.18.0.3:443:0 server certificate does NOT include an ID which matches the server name
2020-12-19 16:42:55,433 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
[Sat Dec 19 16:42:55.450538 2020] [mpm_prefork:notice] [pid 51] AH00163: Apache/2.4.25 (Debian) PHP/7.0.33 OpenSSL/1.0.2q configured -- resuming normal operations
[Sat Dec 19 16:42:55.450673 2020] [core:notice] [pid 51] AH00094: Command line: 'apache2 -D FOREGROUND'

supla:clean:passed-io-client-registration-dates
-----------------------------------------------

Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0

supla:clean:disable-demo-client-apps
------------------------------------

Clients to disable: 0

2020-12-19 16:43:14,820 WARN received SIGTERM indicating exit request
2020-12-19 16:43:14,821 INFO waiting for apache, cron to die
2020-12-19 16:43:14,824 INFO stopped: cron (terminated by SIGTERM)
[Sat Dec 19 16:43:14.908896 2020] [mpm_prefork:notice] [pid 51] AH00169: caught SIGTERM, shutting down
2020-12-19 16:43:14,960 INFO stopped: apache (exit status 0)
Database connection has been established.

                    Application Migrations


No migrations to execute.
Client for webapp exists.

 // Warming up the cache for the prod environment with debug
 // false

 [OK] Cache for the "prod" environment (debug=false) was successfully warmed.

User [email protected] already exists.
2020-12-19 16:43:59,190 CRIT Supervisor running as root (no user in config file)
2020-12-19 16:43:59,199 INFO supervisord started with pid 1
2020-12-19 16:44:00,206 INFO spawned: 'apache' with pid 51
2020-12-19 16:44:00,213 INFO spawned: 'cron' with pid 52
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message
[Sat Dec 19 16:44:00.565176 2020] [ssl:warn] [pid 51] AH01906: 172.18.0.3:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Sat Dec 19 16:44:00.565484 2020] [ssl:warn] [pid 51] AH01909: 172.18.0.3:443:0 server certificate does NOT include an ID which matches the server name
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message
[Sat Dec 19 16:44:00.815429 2020] [ssl:warn] [pid 51] AH01906: 172.18.0.3:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Sat Dec 19 16:44:00.815547 2020] [ssl:warn] [pid 51] AH01909: 172.18.0.3:443:0 server certificate does NOT include an ID which matches the server name
[Sat Dec 19 16:44:00.833731 2020] [mpm_prefork:notice] [pid 51] AH00163: Apache/2.4.25 (Debian) PHP/7.0.33 OpenSSL/1.0.2q configured -- resuming normal operations
[Sat Dec 19 16:44:00.833870 2020] [core:notice] [pid 51] AH00094: Command line: 'apache2 -D FOREGROUND'
2020-12-19 16:44:01,836 INFO success: apache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-12-19 16:44:01,837 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

supla:clean:passed-io-client-registration-dates
-----------------------------------------------

Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0

supla:clean:disable-demo-client-apps
------------------------------------

Clients to disable: 0


supla:clean:passed-io-client-registration-dates
-----------------------------------------------

Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0

supla:clean:disable-demo-client-apps
------------------------------------

Clients to disable: 0

Code: Select all

root@arm-64:~# docker logs --since=5m supla-server
INFO[1608396155.414075] METRICS: USER[COUNT:0] CLIENT[ADD:0 MAX:0 COUNT:0 TRASH:0] DEVICE[ADD:0 MAX:0 COUNT:0 TRASH:0]
2020-12-19 16:43:12,478 WARN received SIGTERM indicating exit request
2020-12-19 16:43:12,479 INFO waiting for supla-scheduler, supla-server to die
INFO[1608396192.479912] Shutting down...
ERR[1608396192.480733] IPC connection accept error 9
ERR[1608396192.481677] Connection accept error 9
ERR[1608396192.482550] Connection accept error 9
INFO[1608396192.484859] Stopped at Sat Dec 19 16:43:12 2020
2020-12-19 16:43:12,558 INFO stopped: supla-server (exit status 0)
INFO[1608396192.559537] Shutting down...
INFO[1608396192.560274] Stopped at Sat Dec 19 16:43:12 2020
2020-12-19 16:43:12,563 INFO stopped: supla-scheduler (exit status 0)
2020-12-19 16:43:30,342 CRIT Supervisor running as root (no user in config file)
2020-12-19 16:43:30,352 INFO supervisord started with pid 1
2020-12-19 16:43:31,359 INFO spawned: 'supla-scheduler' with pid 11
2020-12-19 16:43:31,367 INFO spawned: 'supla-server' with pid 12
INFO[1608396211.390934] Scheduler version 2.3.9
INFO[1608396211.391327] Started at Sat Dec 19 16:43:31 2020
INFO[1608396211.401896] Server version 2.3.27 [Protocol v13]
INFO[1608396211.402322] Started at Sat Dec 19 16:43:31 2020
INFO[1608396211.426653] SSL version: OpenSSL 1.1.0l  10 Sep 2019
2020-12-19 16:43:32,429 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-12-19 16:43:32,430 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Code: Select all

root@arm-64:~# docker logs --since=5m supla-db
2020-12-19 16:43:15 0 [Note] mysqld (initiated by: unknown): Normal shutdown
2020-12-19 16:43:15 0 [Note] Event Scheduler: Purging the queue. 0 events
2020-12-19 16:43:15 0 [Note] InnoDB: FTS optimize thread exiting.
2020-12-19 16:43:15 0 [Note] InnoDB: Starting shutdown...
2020-12-19 16:43:15 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2020-12-19 16:43:15 0 [Note] InnoDB: Buffer pool(s) dump completed at 201219 16:43:15
2020-12-19 16:43:17 0 [Note] InnoDB: Shutdown completed; log sequence number 6797359; transaction id 3968
2020-12-19 16:43:17 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2020-12-19 16:43:17 0 [Note] mysqld: Shutdown complete

2020-12-19 16:43:24+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.3.27+maria~focal started.
2020-12-19 16:43:24+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2020-12-19 16:43:24+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.3.27+maria~focal started.
2020-12-19 16:43:25 0 [Note] mysqld (mysqld 10.3.27-MariaDB-1:10.3.27+maria~focal) starting as process 1 ...
2020-12-19 16:43:25 0 [Note] InnoDB: Using Linux native AIO
2020-12-19 16:43:25 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-12-19 16:43:25 0 [Note] InnoDB: Uses event mutexes
2020-12-19 16:43:25 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-12-19 16:43:25 0 [Note] InnoDB: Number of pools: 1
2020-12-19 16:43:25 0 [Note] InnoDB: Using generic crc32 instructions
2020-12-19 16:43:25 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2020-12-19 16:43:25 0 [Note] InnoDB: Completed initialization of buffer pool
2020-12-19 16:43:25 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-12-19 16:43:26 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-12-19 16:43:26 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-12-19 16:43:26 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-12-19 16:43:26 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2020-12-19 16:43:26 0 [Note] InnoDB: 10.3.27 started; log sequence number 6797359; transaction id 3952
2020-12-19 16:43:26 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2020-12-19 16:43:26 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-12-19 16:43:26 0 [Note] Server socket created on IP: '::'.
2020-12-19 16:43:26 0 [Note] Reading of all Master_info entries succeeded
2020-12-19 16:43:26 0 [Note] Added new Master_info '' to hash table
2020-12-19 16:43:26 0 [Note] mysqld: ready for connections.
Version: '10.3.27-MariaDB-1:10.3.27+maria~focal'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
2020-12-19 16:43:26 0 [Note] InnoDB: Buffer pool(s) load completed at 201219 16:43:26

i try

Code: Select all

./supla-docker/supla.sh restart

but cloud not run

ocean · Post Sat Dec 19, 2020 4:56 pm

i see there are multiple network connections, is it the problem?
i set static IP 192.168.1.99

Code: Select all

root@arm-64:~# ifconfig
br-4e2f22ff2fcc: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        ether 02:42:07:f8:88:f0  txqueuelen 0  (Ethernet)
        RX packets 4  bytes 112 (112.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:9d:85:77:3b  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.99  netmask 255.255.252.0  broadcast 192.168.3.255
        inet6 fe80::4670:3a08:b176:dfbf  prefixlen 64  scopeid 0x20<link>
        ether 8a:1e:cf:15:f6:b9  txqueuelen 1000  (Ethernet)
        RX packets 5832  bytes 362313 (353.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 383  bytes 24255 (23.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 21

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth4878364: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether c6:aa:b8:3f:c3:01  txqueuelen 0  (Ethernet)
        RX packets 170  bytes 23504 (22.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 142  bytes 27822 (27.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth114e0ac: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether be:fc:6b:47:09:03  txqueuelen 0  (Ethernet)
        RX packets 8522  bytes 1214086 (1.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 7945  bytes 1563053 (1.4 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethfa81cbe: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 2e:05:70:2b:dc:31  txqueuelen 0  (Ethernet)
        RX packets 8085  bytes 1590791 (1.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8692  bytes 1237590 (1.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lesny8 · Post Sat Dec 19, 2020 5:54 pm

What do you set in .env file?
CLOUD_DOMAIN=192.168.1.99

What configuration do you set proxy or standalone?
Multiple network interfaces is not a problem. These are docker interfaces for internal connection between containers.

What do you use https:// or http:// when you are trying to connect to the Cloud?
Do you have a computer with an address set in the same pool? Routing is ok? Can you ping server?
I see you have set the netmask to 22