Hello
I have configured this on my server which has a public IP. Now I had some doubts related to registering CNAME records.
Is it compulsory to have https and is it compulsory to register subdomains api, s3, vpn, and registry. Can I register only one DNS for the IP Address?
Also, How can I verify my server is running after assigning the DNS to my IP address?
I get following logs when I run ./scripts/compose up
-> ./scripts/compose up
Starting openbalena_redis_1_918c910c01d3 ... done
Starting openbalena_cert-provider_1_453dfda47d64 ... done
Starting openbalena_s3_1_afe1b57bcb92 ... done
Starting openbalena_db_1_8981f3edc9d9 ... done
Starting openbalena_api_1_b946d63f2941 ... done
Starting openbalena_vpn_1_4f32c78d74e5 ... done
Starting openbalena_registry_1_75517ae0d16c ... done
Starting openbalena_haproxy_1_ea78669dc5c2 ... done
Attaching to openbalena_s3_1_afe1b57bcb92, openbalena_cert-provider_1_453dfda47d64, openbalena_redis_1_918c910c01d3, openbalena_db_1_8981f3edc9d9, openbalena_api_1_b946d63f2941, openbalena_registry_1_75517ae0d16c, openbalena_vpn_1_4f32c78d74e5, openbalena_haproxy_1_ea78669dc5c2
s3_1_afe1b57bcb92 | Systemd init system enabled.
cert-provider_1_453dfda47d64 | [Error] ACTIVE variable is not enabled. Value should be "true" or "yes" to continue.
cert-provider_1_453dfda47d64 | [Error] Unable to continue due to misconfiguration. See errors above. [Stopping]
redis_1_918c910c01d3 | 1:C 09 May 2019 13:22:11.707 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1_918c910c01d3 | 1:C 09 May 2019 13:22:11.707 # Redis version=5.0.4, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1_918c910c01d3 | 1:C 09 May 2019 13:22:11.707 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1_918c910c01d3 | 1:M 09 May 2019 13:22:11.709 * Running mode=standalone, port=6379.
redis_1_918c910c01d3 | 1:M 09 May 2019 13:22:11.709 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1_918c910c01d3 | 1:M 09 May 2019 13:22:11.709 # Server initialized
redis_1_918c910c01d3 | 1:M 09 May 2019 13:22:11.709 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1_918c910c01d3 | 1:M 09 May 2019 13:22:11.709 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1_918c910c01d3 | 1:M 09 May 2019 13:22:11.709 * DB loaded from disk: 0.000 seconds
redis_1_918c910c01d3 | 1:M 09 May 2019 13:22:11.709 * Ready to accept connections
db_1_8981f3edc9d9 | 2019-05-09 13:22:12.097 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
db_1_8981f3edc9d9 | 2019-05-09 13:22:12.097 UTC [1] LOG: listening on IPv6 address "::", port 5432
db_1_8981f3edc9d9 | 2019-05-09 13:22:12.112 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1_8981f3edc9d9 | 2019-05-09 13:22:12.182 UTC [21] LOG: database system was shut down at 2019-05-09 13:21:54 UTC
db_1_8981f3edc9d9 | 2019-05-09 13:22:12.195 UTC [1] LOG: database system is ready to accept connections
api_1_b946d63f2941 | Systemd init system enabled.
registry_1_75517ae0d16c | Systemd init system enabled.
vpn_1_4f32c78d74e5 | Systemd init system enabled.
haproxy_1_ea78669dc5c2 | Building certificate from environment variables...
haproxy_1_ea78669dc5c2 | Setting up watches. Beware: since -r was given, this may take a while!
haproxy_1_ea78669dc5c2 | Watches established.
haproxy_1_ea78669dc5c2 | [NOTICE] 128/132214 (15) : New worker #1 (17) forked
haproxy_1_ea78669dc5c2 | [WARNING] 128/132214 (17) : Server backend_api/resin_api_1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
haproxy_1_ea78669dc5c2 | [ALERT] 128/132214 (17) : backend 'backend_api' has no server available!
haproxy_1_ea78669dc5c2 | [WARNING] 128/132215 (17) : Server backend_registry/resin_registry_1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
haproxy_1_ea78669dc5c2 | [ALERT] 128/132215 (17) : backend 'backend_registry' has no server available!
haproxy_1_ea78669dc5c2 | [WARNING] 128/132216 (17) : Server vpn-tunnel/balena_vpn is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
haproxy_1_ea78669dc5c2 | [ALERT] 128/132216 (17) : proxy 'vpn-tunnel' has no server available!
db_1_8981f3edc9d9 | 2019-05-09 13:22:18.418 UTC [28] ERROR: relation "uniq_model_model_type_vocab" already exists
db_1_8981f3edc9d9 | 2019-05-09 13:22:18.418 UTC [28] STATEMENT: CREATE UNIQUE INDEX "uniq_model_model_type_vocab" ON "model" ("is of-vocabulary", "model type");
haproxy_1_ea78669dc5c2 | [WARNING] 128/132219 (17) : Server backend_registry/resin_registry_1 is UP, reason: Layer4 check passed, check duration: 0ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
haproxy_1_ea78669dc5c2 | [WARNING] 128/132220 (17) : Server vpn-tunnel/balena_vpn is UP, reason: Layer4 check passed, check duration: 0ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
haproxy_1_ea78669dc5c2 | [WARNING] 128/132224 (17) : Server backend_api/resin_api_1 is UP, reason: Layer4 check passed, check duration: 0ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
I am not sure if my server is running properly.