[COMPASS-4219] Clicking Connect on known working connection string blanks form and never connects or errors Created: 30/Mar/20 Updated: 30/Sep/20 Resolved: 30/Sep/20 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Compass |
| Affects Version/s: | 1.20.5 |
| Fix Version/s: | No version |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Max Young | Assignee: | Rhys Howell |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 10 |
||
| Attachments: |
|
| Documentation Changes: | Not Needed |
| Sprint: | Iteration Blackberry, Iteration Cantaloupe, Iteration Dragon Fruit, Iteration Elderberry, Iteration Fig, Iteration Guanábana, Iteration Huckleberry, Iteration Icaco, Iteration Jackfruit, Iteration Kiwi |
| Description |
|
Connection string (from Atlas) I am connecting to the instance using Robo 3T and was previously connecting using Compass so I suspect the issue is new since this release. I tried to attach a screenshot but get "Jira could not attach the file as there was a missing token. Please try attaching the file again. although it does appear for me below."
|
| Comments |
| Comment by Rhys Howell [ 26/Aug/20 ] | |
|
Hi maxy@ambrosebuilding.com.au - this is an interesting issue. Do you know if the same issue exists when you're on a different internet connection? This could be a DNS issue which is why when turning on your VPN the issue goes away. My previous ISP's default DNS didn't resolve some atlas urls correctly. This might help us debug a little - which public DNS is your system? Could you try configuring your system's public DNS to use something like google's: https://developers.google.com/speed/public-dns/docs/using The other side of this issue is that the UI goes into an idle state where you can't do anything. I've filed a ticket which hopefully will help those cases so we can be less ambiguous when a connection is having trouble resolving: https://jira.mongodb.org/browse/COMPASS-4393 | |
| Comment by Max Young [ 14/Apr/20 ] | |
|
Sorry for the delay - yes it is longer than 30 seconds. I have left it in that state for many many minutes -possibly hours (I just left it there). My General.json is also pasted below (in case it is useful) Note that this was working again yesterday, all day - shut down last night, tried again this morning and back to this strange not working state - to my knowledge nothing has been updated or changed on my computer in the meantime. Robo 3T connects and works just fine.
General.json
| |
| Comment by Massimiliano Marcon [ 09/Apr/20 ] | |
|
maxy@ambrosebuilding.com.au the timeout is 30 seconds, so if there is something wrong with the connection Compass may stay in that state for up to 30 seconds. Can you please confirm if you've waited 30 seconds? Also, can you try again to upload the screenshot? | |
| Comment by Max Young [ 06/Apr/20 ] | |
|
This looks like it is related to network accessibility. Although my current IP address is whitelisted, this 'greying out and never completing' issue happens every time for me on my cluster. If I start my VPN, then it does connect. I have an entry 0.0.0.0/0 which, I thought, should let all addresses through. Not to distract from the actual problem which is that the client never returns or gives any indication that anything is wrong. |