Unable to connect to tile38

[mapsgeek]

I run tile38 image on port 9851 and it listens through the cli and able to execute commands then i run tile38-viewer via docker run 8080:80 <image-id> when i open the browser on port 8080 the app can't connect to the server leaving this error

warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3] Failed to determine the https port for redirect. fail: tile38_viewer.Controllers.Tile38Controller[0] Unable to connect to Tile38

[smarianimore]

I get a similar error on Windows 10 Home, Version: 20H2, Build: 19042.1237 I do not run Tile38 server separately as it is already launched as part of the docker-compose command. Thus, I only run the docker-compose but get the following error log (basically, can't connect to Tile38, seemingly because of "Failed to determine the https port for redirect" by Redis):

warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]
      No XML encryptor configured. Key {37e527e9-81be-4f5f-9418-c01359de4e81} may be persisted to storage in unencrypted form.
Hosting environment: Production
Content root path: /app
Now listening on: http://[::]:80
Application started. Press Ctrl+C to shut down.
warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3]
      Failed to determine the https port for redirect.
fail: tile38_viewer.Controllers.Tile38Controller[0]
      Unable to connect to Tile38
StackExchange.Redis.RedisConnectionException: It was not possible to connect to the redis server(s). UnableToConnect on ec2-52-64-153-27.ap-southeast-2.compute.amazonaws.com:9851/Interactive, Initializing/NotStarted, last: NONE, origin: BeginConnectAsync, outstanding: 0, last-read: 0s ago, last-write: 0s ago, keep-alive: 60s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.0.601.3402
   at StackExchange.Redis.ConnectionMultiplexer.ConnectImpl(Object configuration, TextWriter log) in C:\projects\stackexchange-redis\src\StackExchange.Redis\ConnectionMultiplexer.cs:line 955
   at tile38_viewer.Controllers.Tile38Controller.GeoFences() in /app/Controllers/api/Tile38Controller.cs:line 44
fail: tile38_viewer.Controllers.Tile38Controller[0]
      Unable to connect to Tile38
StackExchange.Redis.RedisConnectionException: It was not possible to connect to the redis server(s). UnableToConnect on ec2-52-64-153-27.ap-southeast-2.compute.amazonaws.com:9851/Interactive, Initializing/NotStarted, last: NONE, origin: BeginConnectAsync, outstanding: 0, last-read: 0s ago, last-write: 0s ago, keep-alive: 60s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.0.601.3402
   at StackExchange.Redis.ConnectionMultiplexer.ConnectImpl(Object configuration, TextWriter log) in C:\projects\stackexchange-redis\src\StackExchange.Redis\ConnectionMultiplexer.cs:line 955
   at tile38_viewer.Controllers.Tile38Controller.KEYS(String filter) in /app/Controllers/api/Tile38Controller.cs:line 105
fail: tile38_viewer.Controllers.Tile38Controller[0]
      Unable to connect to Tile38
StackExchange.Redis.RedisConnectionException: It was not possible to connect to the redis server(s). UnableToConnect on ec2-52-64-153-27.ap-southeast-2.compute.amazonaws.com:9851/Interactive, Initializing/NotStarted, last: NONE, origin: BeginConnectAsync, outstanding: 0, last-read: 0s ago, last-write: 0s ago, keep-alive: 60s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 23s ago, v: 2.0.601.3402
   at StackExchange.Redis.ConnectionMultiplexer.ConnectImpl(Object configuration, TextWriter log) in C:\projects\stackexchange-redis\src\StackExchange.Redis\ConnectionMultiplexer.cs:line 955
   at tile38_viewer.Controllers.Tile38Controller.KEYS(String filter) in /app/Controllers/api/Tile38Controller.cs:line 105
fail: tile38_viewer.Controllers.Tile38Controller[0]
      Unable to connect to Tile38
StackExchange.Redis.RedisConnectionException: It was not possible to connect to the redis server(s). UnableToConnect on ec2-52-64-153-27.ap-southeast-2.compute.amazonaws.com:9851/Interactive, Initializing/NotStarted, last: NONE, origin: BeginConnectAsync, outstanding: 0, last-read: 0s ago, last-write: 0s ago, keep-alive: 60s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 23s ago, v: 2.0.601.3402
   at StackExchange.Redis.ConnectionMultiplexer.ConnectImpl(Object configuration, TextWriter log) in C:\projects\stackexchange-redis\src\StackExchange.Redis\ConnectionMultiplexer.cs:line 955
   at tile38_viewer.Controllers.Tile38Controller.GeoFences() in /app/Controllers/api/Tile38Controller.cs:line 44
Application is shutting down...
Hosting environment: Production
Content root path: /app
Now listening on: http://[::]:80
Application started. Press Ctrl+C to shut down.

Any help?

[relet]

In my case, it tries to connect to an AWS instance, which seems to be a default value.

My server is running on a local network 192.168.5.1:9851. I have specified the following ConnectionStrings:Tile38Connection=192.168.5.1:9851 in docker-environment-list.

I still get an error like

{"message":"Unable to connect to Tile38",
"exception":{"ClassName":"StackExchange.Redis.RedisConnectionException","Message":"It was not possible to connect to the redis server(s). UnableToConnect on ec2-52-64-153-27.ap-southeast-2.compute.amazonaws.com:9851/Interactive, Initializing/NotStarted, last: NONE, origin: BeginConnectAsync, outstanding: 0, last-read: 0s ago, last-write: 0s ago, keep-alive: 60s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 384s ago, v: 2.0.601.3402","Data":null,"InnerException":null,"HelpURL":null,"StackTraceString":"   at StackExchange.Redis.ConnectionMultiplexer.ConnectImpl(Object configuration, TextWriter log) in C:\\projects\\stackexchange-redis\\src\\StackExchange.Redis\\ConnectionMultiplexer.cs:line 955\n   at tile38_viewer.Controllers.Tile38Controller.GeoFences() in /app/Controllers/api/Tile38Controller.cs:line 44","RemoteStackTraceString":null,"RemoteStackIndex":0,"ExceptionMethod":null,"HResult":-2146233088,"Source":"StackExchange.Redis","WatsonBuckets":null,"failureType":9,"commandStatus":0}}

[relet]

I traced the issue down to the containers not accepting the docker-environment-list at all. If I exec /bin/bash inside the tile38-worker and tile38-viewer containers to the correct values, both create a correct connection immediately.