Connection refused on-premises local docker

[eugeneniemand]

I'm trying the On-Premises docker image and it all works fine running at http://localhost:9054/ I have a DSL/JSON that was generated with the latest Lite version and also works fine. When I run the following CLI command

docker run -it --rm -v C:\git\Architecture\C4\Current:/usr/local/structurizr structurizr/cli push -id 2 -key 6795299b-f99f-4b75-ba02-0ca730bc3cb6 -secret 6795299b-f99f-4b75-ba02-0ca730bc3cb6 -workspace workspace.json -url http://localhost:9054/

I get this error

Pushing workspace 2 to http://localhost:9054/
 - creating new workspace
 - parsing model and views from /usr/local/structurizr/workspace.json
 - merge layout from remote: true
 - storing previous version of workspace in null
 - pushing workspace
Getting workspace with ID 2
org.apache.hc.client5.http.HttpHostConnectException: Connect to http://localhost:9054 [localhost/127.0.0.1] failed: Connection refused
com.structurizr.api.StructurizrClientException: org.apache.hc.client5.http.HttpHostConnectException: Connect to http://localhost:9054 [localhost/127.0.0.1] failed: Connection refused
com.structurizr.api.StructurizrClientException: com.structurizr.api.StructurizrClientException: org.apache.hc.client5.http.HttpHostConnectException: Connect to http://localhost:9054 [localhost/127.0.0.1] failed: Connection refused
        at com.structurizr.api.StructurizrClient.putWorkspace(StructurizrClient.java:420)
        at com.structurizr.cli.PushCommand.run(PushCommand.java:137)
        at com.structurizr.cli.StructurizrCliApplication.run(StructurizrCliApplication.java:77)
        at com.structurizr.cli.StructurizrCliApplication.main(StructurizrCliApplication.java:112)
Caused by: com.structurizr.api.StructurizrClientException: org.apache.hc.client5.http.HttpHostConnectException: Connect to http://localhost:9054 [localhost/127.0.0.1] failed: Connection refused
        at com.structurizr.api.StructurizrClient.getWorkspace(StructurizrClient.java:353)
        at com.structurizr.api.StructurizrClient.putWorkspace(StructurizrClient.java:373)
        ... 3 more
Caused by: org.apache.hc.client5.http.HttpHostConnectException: Connect to http://localhost:9054 [localhost/127.0.0.1] failed: Connection refused
        at java.base/sun.nio.ch.Net.pollConnect(Native Method)
        at java.base/sun.nio.ch.Net.pollConnectNow(Unknown Source)
        at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(Unknown Source)
        at java.base/sun.nio.ch.NioSocketImpl.connect(Unknown Source)
        at java.base/java.net.SocksSocketImpl.connect(Unknown Source)
        at java.base/java.net.Socket.connect(Unknown Source)
        at org.apache.hc.client5.http.socket.PlainConnectionSocketFactory.lambda$connectSocket$0(PlainConnectionSocketFactory.java:85)
        at java.base/java.security.AccessController.doPrivileged(Unknown Source)
        at org.apache.hc.client5.http.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:84)
        at org.apache.hc.client5.http.socket.ConnectionSocketFactory.connectSocket(ConnectionSocketFactory.java:113)
        at org.apache.hc.client5.http.impl.io.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:181)
        at org.apache.hc.client5.http.impl.io.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:447)
        at org.apache.hc.client5.http.impl.classic.InternalExecRuntime.connectEndpoint(InternalExecRuntime.java:162)
        at org.apache.hc.client5.http.impl.classic.InternalExecRuntime.connectEndpoint(InternalExecRuntime.java:172)
        at org.apache.hc.client5.http.impl.classic.ConnectExec.execute(ConnectExec.java:142)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
        at org.apache.hc.client5.http.impl.classic.ProtocolExec.execute(ProtocolExec.java:192)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
        at org.apache.hc.client5.http.impl.classic.HttpRequestRetryExec.execute(HttpRequestRetryExec.java:96)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
        at org.apache.hc.client5.http.impl.classic.ContentCompressionExec.execute(ContentCompressionExec.java:152)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
        at org.apache.hc.client5.http.impl.classic.RedirectExec.execute(RedirectExec.java:115)
        at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
        at org.apache.hc.client5.http.impl.classic.InternalHttpClient.doExecute(InternalHttpClient.java:170)
        at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:123)
        at com.structurizr.api.StructurizrClient.getWorkspace(StructurizrClient.java:318)
        ... 4 more

[simonbrowndotje]

Is http://localhost:9054 accessible from inside the CLI Docker container? If not, that's your problem, and you'll need to configure a network route between the CLI container and the on-premises container.

[eugeneniemand]

I'm getting further, still getting errors but now its structurizr errors
docker run -it --rm --network host -v C:\git\DataServices.Architecture\C4\Current:/usr/local/structurizr structurizr/cli push -id 2 -key 6795299b-f99f-4b75-ba02-0ca730bc3cb6 -secret 6795299b-f99f-4b75-ba02-0ca730bc3cb6 -workspace workspace.json -url http://localhost:9054/

Pushing workspace 2 to http://localhost:9054/
 - creating new workspace
 - parsing model and views from /usr/local/structurizr/workspace.dsl
SystemContext-001 is an automatically generated view key - you will likely lose manual layout information when using automatically generated view keys.
Container-001 is an automatically generated view key - you will likely lose manual layout information when using automatically generated view keys.
SystemContext-002 is an automatically generated view key - you will likely lose manual layout information when using automatically generated view keys.
Container-002 is an automatically generated view key - you will likely lose manual layout information when using automatically generated view keys.
 - merge layout from remote: true
 - storing previous version of workspace in null
 - pushing workspace
Getting workspace with ID 2
com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false')
 at [Source: (StringReader); line: 1, column: 2]
...

[eugeneniemand]

I've just tried validation on both the DSL & JSON and that all succeeds

docker run -it --rm --network host -v C:\git\DataServices.Architecture\C4\Current:/usr/local/structurizr structurizr/cli validate --workspace workspace.dsl                      

Validating workspace at workspace.dsl
SystemContext-001 is an automatically generated view key - you will likely lose manual layout information when using automatically generated view keys.
Container-001 is an automatically generated view key - you will likely lose manual layout information when using automatically generated view keys.
SystemContext-002 is an automatically generated view key - you will likely lose manual layout information when using automatically generated view keys.
Container-002 is an automatically generated view key - you will likely lose manual layout information when using automatically generated view keys.
 - validated
 - finished

docker run -it --rm --network host -v C:\git\DataServices.Architecture\C4\Current:/usr/local/structurizr structurizr/cli validate --workspace workspace.json

Validating workspace at workspace.json
 - validated
 - finished

[simonbrowndotje]

validate just loads the workspace into memory to show that your JSON/DSL is valid. I suspect you have the API URL incorrect, and it should probably be http://localhost:9054/api (the workspace settings page should have this information).

[eugeneniemand]

Great thanks I'm making progress. I hope this is the last issue
com.structurizr.api.StructurizrClientException: com.structurizr.api.StructurizrClientException: com.structurizr.api.StructurizrClientException: Authorization header doesn't match

[simonbrowndotje]

It means the API key/secret is probably incorrect. From the command you posted above, I can see that you've specified the same value for both the key and secret.

-key 6795299b-f99f-4b75-ba02-0ca730bc3cb6 -secret 6795299b-f99f-4b75-ba02-0ca730bc3cb6

Again, the workspace settings page will have that information.