[COMPASS-1864] Proxy Configuration Created: 30/Aug/17 Updated: 17/Jul/20 Resolved: 24/Sep/19 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Connectivity |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Davide De Angelis | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 4 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Hello! The customer is using Compass behind a Corporate Proxy and can't connect to its MongoDB Deployments in MLAB. I suggested using the built-in SSH Tunneling feature of Compass, but it could be a good candidate for a feature request. Thank you! |
| Comments |
| Comment by Kirill Temnenkov [ 28/Sep/19 ] |
|
Well, I’ll search for another NoSql database. |
| Comment by Massimiliano Marcon [ 24/Sep/19 ] |
|
Not something we are considering at this time. |
| Comment by Kirill Temnenkov [X] [ 08/Jun/18 ] |
|
I am from Russia, I wanna connect to ip 34.195.121.130 (cluster0-shard-00-00-jxeqq.mongodb.net is ec2-34-195-121-130.compute-1.amazonaws.com), 34.195.121.130 is blocked by our organization "roskomnadzor" in his fight with the Telegram. |
| Comment by Brian Blevins [ 17/Oct/17 ] |
|
Another enterprise customer that would likely benefit from the ability to use a standard HTTP/SOCKS proxy to access Atlas clusters over the Internet. This customer is using an SSH bastion host to workaround the lack of this feature. |
| Comment by Davide De Angelis [ 30/Aug/17 ] |
|
intercome conversation link https://app.intercom.io/a/apps/p57suhg7/respond/inbox/1433646/conversations/11504899037 |