On Tue, Jul 16, 2019, at 3:06 PM, dancab@caltech.edu wrote:
Accessing the API via localhost works fine and I haven't encountered any issues. It's only with my 'proxy' solution for remote access that I have problems.
However, using curl seems to work either way.
This is the curl output via the Docker container connecting directly to localhost:8001.
{"start": 0, "total_size": 1, "entries": [{"alias_domain": "", "description": "Caltech Mailing List Service", "mail_host": "caltech.edu", "self_link": "http://localhost:8001/3.1/domains/caltech.edu", "http_etag": "\"e855d96f0362738a0f174fd24c8595b62761d496\""}], "http_etag": "\"333b74d5a650c199065262450afc1f5521f87db2\""}
This is the curl output connecting from my desktop to the same container remotely via Apache virtual host proxy. It seems fine!
{"start": 0, "total_size": 1, "entries": [{"alias_domain": "", "description": "Caltech Mailing List Service", "mail_host": "caltech.edu", "self_link": "http://localhost:8001/3.1/domains/caltech.edu", "http_etag": "\"e855d96f0362738a0f174fd24c8595b62761d496\""}], "http_etag": "\"333b74d5a650c199065262450afc1f5521f87db2\""}
Does it *always* happen when running client.domains or does it
happen randomly on any client. call?
I was thinking if there could be an issue with total number of open connections over the ssh tunnel that you have setup, causing connection refused after a limit has been reached. max_sessions and max_startup options could help with that. I'd have to read up more on how the sessions work with ssh tunnel.
Any ideas?
This is a totally wild guess, but maybe using a different HTTP library could change something. The latest master of mailmanclient has moved to using requests as compared to Httplib2 from your installed version.
You can install a test version from Gitlab's master branch[1]. I will soon cut out a release, but that should help debug the problem.
[1] https://gitlab.com/mailman/mailmanclient
-- thanks, Abhilash Raj (maxking)