James Hillyerd

Just tried the above config via `docker-compose -f inbucket.yml up` and the monitor is working for me. Docker version 18.01.0-ce, build 03596f5 docker-compose version 1.17.1, build unknown Have you tried...

I wouldn't expect the docker version to play a significant role unless they were drastically different. I'm not clear how much troubleshooting you have done so far, please be explicit....

Do you have https://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html enabled? I haven't touched Apache in years, so I can't help much here - but this may be another one worth documenting if you can get...

The start script inside the container lives here: https://github.com/jhillyerd/inbucket/blob/master/etc/docker/defaults/start-inbucket.sh I don't see it specifying a log file, so I'm pretty sure it's logging to stdout or stderr

Inbucket Monitor is my first and only experience with websocket, so I'm not very knowledgeable on how it works. but you might be able to leverage packet capture to compare...

The demo site is now built with docker-compose: https://github.com/jhillyerd/demo.inbucket.org When I have time I'll play around with reverse proxy + Let's Encrypt.

@Xotabu4 I think you are running into #128 - which is fixed in current development tree. Beware that the `latest` docker build seems to be broken though - #134

Interesting idea. Potential downside is for many feed readers to work, you'd have to expose Inbuckets UI to the internet. For now, this will be blocked on the [UI revamp](https://github.com/jhillyerd/inbucket/projects/3)...

You might try changing the [mailbox naming parameter](https://github.com/inbucket/inbucket/blob/main/doc/config.md#mailbox-naming). By default, Inbucket throws away the domain part of the address, so we wouldn't be able to display it (in otherwords, [email protected]...

#255 took care of most of these.