-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Anyone else getting Connection Failed just like if they were using the horrible java way? #5
Comments
Not sure if this is relevant, but I'll add this.
|
Can you attach a complete log file? Does the console work outside of Docker? Do you have an iDRAC 6 Enterprise module installed and is it recognized correctly? This can be checked on the top left corner of the iDRAC web interface. |
Sure, sorry didn't wan't to just throw a huge log out there. Here's the full log. It does say Enterprise in the top left corner. It works fine, just not on the new macOS which is why I'm trying to set something else up.
|
Could you also post the docker-compose or Docker command you used? |
I used the docker-compose included, just modified the username, password, and host. One thing I can think of that may be an issue is that my host is example.com:8443 |
Yes, that's definitely a problem. Can you try switching to 443 temporarily and only set IDRAC_HOST to example.com? |
I can't. My idrac doesn't have its own ip and I have Apache on 443.
…On Mon, Nov 19, 2018 at 8:56 AM Dominik ***@***.***> wrote:
One thing I can think of that may be an issue is that my host is
example.com:8443
Yes, that's definitely a problem. Can you try switching to 443 temporarily
and only set IDRAC_HOST to example.com?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AL3iRJaWGLzrdROlAVez4e1rmJecLA6Rks5uwriigaJpZM4YoAGw>
.
|
If you have an iDRAC Enterprise it should have its own NIC on the back, assuming you have set iDRAC to dedicated instead of shared in the BIOS. As a workaround you can also add a volume to /app and start the container once. After the container comes up with the error message, restart the container with IDRAC_HOST set to example.org. That should make it use the cached .jars but still connect to the correct address. |
Yeah I'm just connecting remotely, without a VPN. Using external ip. That's why I set the port to 8443 since I'm port forwarding. |
The correct address is specifying a port as you can set in the idrac config. Not just assuming everyone uses the default. |
You mean the Docker container is not running locally or you have port forwarded the Docker container and access it remotely? Can you try any of the variants above? I will add a separate port parameter once you can confirm that this is indeed the issue. |
The network that the idrac and servers are on have a single external ip, a router port forwards ports 80/443 among others to a server, and 8443 to the idrac. Docker is running locally. |
And if I try to remove the port it tries to redownload the .jar's and fails. |
Did you add a volume to /app? |
I'm not sure what that means. |
I just added the http-port branch so you can try it. Just edit your docker-compose like this:
Adjust the image to domistyle/idrac6:http-port and add the IDRAC_PORT environment variable. Remove any ports from IDRAC_HOST. |
I've specified the port like you have there, but seems it's still trying to connect on 443. |
Works fine for me, did you recreate the container with |
Yep.
|
Can you post the new docker-compose.yml? |
|
Switch out |
Well, it connected and downloaded now, but still getting the connection failed message.
|
At least we're getting a real error message now. Make sure the Docker container can reach port 5900 on your iDRAC and example.org is really pointing at your iDRAC and not a proxy in front of it. I am not sure if you can use virtual console with a shared NIC though, I never tried. Since you said you used it previously I'm just going to assume it works. |
Well if I telnet to that port I get a connection, and would assume docker could too? But yeah, I've been using my idrac with this port forwarding setup for years. 5900 is forwarded to idrac. |
Wait. It just loaded. Seems after a few failures it actually connected. |
Does it work reliably now? |
Yep, seems like everything is good. So nice to be able to use my iDRAC again. Thanks for your help with this :) |
Good to hear. I'm going to close this issue then and merge the changes to master. |
See the image
The text was updated successfully, but these errors were encountered: