juju deploy failed with "tcp: tls" error message


Hi all,

I have created a MAAS cloud and setup a controller already, $ juju status
Model Controller Cloud/Region Version SLA Timestamp
default maas-cloud-control maascloud 2.4.4 unsupported 16:50:34+08:00

Machine State DNS Inst id Series AZ Message
0 started fxcmyn xenial default Deployed

But if want to deploy anything like “juju-gui”, it will consistently failed with the below error message,

$ juju deploy --to 0 juju-gui

ERROR storing charm for URL “cs:juju-gui-142”: cannot retrieve charm “cs:juju-gui-142”: cannot get archive: Get https://api.jujucharms.com/charmstore/v5/juju-gui-142/archive?channel=stable: proxyconnect tcp: tls: oversized record received with length 20527

I have googled for an while, looks like to me it is related with https/http connection, is there any configuration in “juju” or “MAAS” that can switch from https to http? The proxy used in MAAS is set to built-in.

Thank you in the advance for any kind of comments!


What proxy is there in MAAS? You might need to change the Juju config for the proxy if there’s one. If the Juju controller (on the maas node) isn’t able to get the url from the charmstore it’ll not work.


There’s some notes in the docs around proxy setup here:


And some other notes throughout the docs.


Thanks rick!

Seems it’s okay to download the charmstore in the controller node, and MAAS proxy is set to built-in.

$ wget https://api.jujucharms.com/charmstore/v5/juju-gui-142/archive?channel=stable
–2018-11-27 04:33:11-- https://api.jujucharms.com/charmstore/v5/juju-gui-142/archive?channel=stable
Connecting to… connected.
Proxy request sent, awaiting response… 200 OK
Length: 10917117 (10M) [application/zip]
Saving to: ‘archive?channel=stable’

archive?channel=stable 100%[=======================================================================================>] 10.41M 1.42MB/s in 8.6s

2018-11-27 04:33:21 (1.21 MB/s) - ‘archive?channel=stable’ saved [10917117/10917117]

I am still cannot get it through, just download and deploy it in the offline mode.