Database connection has been established.
Application Migrations
No migrations to execute.
// 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.
2018-06-04 06:13:49,589 CRIT Supervisor running as root (no user in config file)
2018-06-04 06:13:49,601 INFO supervisord started with pid 1
2018-06-04 06:13:50,607 INFO spawned: 'apache' with pid 49
2018-06-04 06:13:50,614 INFO spawned: 'cron' with pid 50
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
[Mon Jun 04 06:13:51.043226 2018] [ssl:warn] [pid 49] AH01906: 172.18.0.3:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Mon Jun 04 06:13:51.043648 2018] [ssl:warn] [pid 49] 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
[Mon Jun 04 06:13:51.366009 2018] [ssl:warn] [pid 49] AH01906: 172.18.0.3:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Mon Jun 04 06:13:51.366123 2018] [ssl:warn] [pid 49] AH01909: 172.18.0.3:443:0 server certificate does NOT include an ID which matches the server name
[Mon Jun 04 06:13:51.383348 2018] [mpm_prefork:notice] [pid 49] AH00163: Apache/2.4.10 (Debian) PHP/7.0.26 OpenSSL/1.0.1t configured -- resuming normal operations
[Mon Jun 04 06:13:51.383470 2018] [core:notice] [pid 49] AH00094: Command line: 'apache2 -D FOREGROUND'
2018-06-04 06:13:52,386 INFO success: apache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-06-04 06:13:52,387 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Schedules to regenerate: 0
Deleted expired scheduled executions: 0
SUPLA-CLOUD v2.2 oficjalnie wydany
-
dawkor
- Posts: 145
- Joined: Sun Jan 07, 2018 1:20 pm
no to mam tak
, ale teraz zauwazylem ze suplascript tez przestala dzialac 
-
dawkor
- Posts: 145
- Joined: Sun Jan 07, 2018 1:20 pm
Cos mi się zdaje ze będę wszystko na nowo robił hehe
-
dawkor
- Posts: 145
- Joined: Sun Jan 07, 2018 1:20 pm
Z logow moze i tak ale rzeczywistosc jest inna. Chyba ze na jakis innych portach
o ktorych niewiem. Scipts tez przestal dzialac.
-
dawkor
- Posts: 145
- Joined: Sun Jan 07, 2018 1:20 pm
nie używam ani letscrypt ani proxy, rozróżniam jedynie portami.

scripts już działa poprawie, zrobiłem reinstalacje. nawet strona działa ale cloud niedawkor@serwer:~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a653a4d65b05 supla_supla-server "/usr/bin/server-ent…" 25 hours ag o Up 25 hours 0.0.0.0:2015-2016->2015-2016/tcp supla-server
2e8d575901bd supla_supla-cloud "docker-php-entrypoi…" 25 hours ag o Up 25 hours 80/tcp supla-cloud
8352d1927bdf hypriot/rpi-mysql:5.5 "/entrypoint.sh mysq…" 25 hours ag o Up 25 hours 3306/tcp supla-db
dawkor@serwer:~ $
-
effendi_pl
- Posts: 24
- Joined: Tue Jun 19, 2018 7:50 am
Cześć, mam następujący problem po update do clouda v.2.2 na docker'ze RPi - nie mogę zalogować się przez stronę www. Po otwarciu strony logowania i po podaniu logina i hasła strona próbuje przenieść mnie na stary adres ip, na którym kiedyś działał serwer - i oczywiście nie znajduje go. Cashe przeglądarki wyczyszczone.Gdzie w konfigach zmieenić te ustawienia?
