Connection refused about ipam HOT 4 CLOSED

Hi @TheMorganator, thanks so much for reaching out. It's clear that for some reason the IPAM solution didn't deploy correctly. Here's a few things to try:

1. Verify that you've met all of the prerequisites from our docs page: https://azure.github.io/ipam/#/deployment/README?id=prerequisites

2. Attach here or send me the log from the deployment, located in the "logs" folder. This was created when you ran the deloy.

As I tell everyone, feel free to reach out to me directly at [email protected] if you'd like some 1:1 troubleshooting, or just don't feel comfortable sharing more details here.

Thanks and hopefully we'll get you up and running ASAP!

from ipam.

Hey @TheMorganator, I know we worked together outside of this thread on this issue. I've also added documentation to help troubleshoot this for future users, which you can review here:

https://azure.github.io/ipam/#/troubleshooting/README?id=disablekeybasedmetadatawriteaccess-cosmos-db

I just want to make sure you're satisfied with everything and if so, let me know if it's OK to close this issue now, or if there's something further that needs to be done.

Thank you, and by the way....all of the latest/greatest code is now pushed to the main branch, and the production container have been updated. Hope you enjoy!

from ipam.

Good morning @TheMorganator, just wanted to circle back with you on this. As mentioned above, the fix for this is now incorporated into the main codebase (including updated docs). If you have any issues, please let me know so we can get you fixed up right away, otherwise confirm if I'm ok to close this issue if everything is resolved. Thank you so much for your partnership!

from ipam.

Hello @TheMorganator , as this fix has been incorporated for a while now, and I haven't heard back from you, I'm hoping all is working well and you're enjoying the Azure IPAM tool. I'm going to close this issue for now, but if at any point you're still seeing this issue (or any other for that matter), please do not hesitate to open another issue, or reach out directly to us. We're always here to help!

from ipam.