Joan

With published 0.1.7 formidable 1.0.14 and gridfs-stream: 0.5.0 This problem reapears. I've updated to: formidable 1.0.16 and gridfs-stream: 0.5.3 all test passed and empty file posts parsed ok!

Hi @ohemorange, ok, don't get confused. All servers launched at wetopi, by default are launched with its letsencrypt cert when running under subdomains. Then, when you move to your own...

I'm experiencing same issue running `17.03.0-ce` ```sh root@dk1w:~# docker info Containers: 14 Running: 10 Paused: 0 Stopped: 4 Images: 21 Server Version: 17.03.0-ce Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing...

We are labeling containers (instead of services), with `docker service create --container-label SERVICE_80_NAME=wp-nginx-{{podId}}{{container_suffix}} ...` this way our registrator can see it ;) On 1 February 2017 at 16:14, marcuslinke wrote:...

@sulphur If you don't expose your ports to the host, run registrator with the option to register "the exposed" ports: ``` -internal Use exposed ports instead of published ports ```

Confirmed, same error.