Thanks for reaching out, and I'm sorry you're running into this error! I've opened a case on your behalf to connect you with a support engineer that can lend you a hand on sorting this out!
It goes back and forth from "couldn't open port" to telling me to "sign in to articulate 360 - click to launch your web browser to sign into Articulate 360."
I am able to log into the browser, but Articulate 360 still doesn't work.
Thanks for sharing those images! Let's see if we can get this sorted out. If you are on a corporate network, ask your IT department to review the following article to allowlist the right endpoints for your Articulate 360 apps to work properly:
deleted ip from IP listen list, put 0.0.0.0 instead = > resolved.
in my case, the problem happened because a couple of years ago I installed and configured some web server on my workstation, then deleted it and forgot.
but anyways, the bottom line is that the problem did not have anything to do with the firewall/service shortage/client version.
4 Replies
Hi Renaldo,
Thanks for reaching out, and I'm sorry you're running into this error! I've opened a case on your behalf to connect you with a support engineer that can lend you a hand on sorting this out!
Be on the lookout for a reply soon!
Hi Ren,
I am getting the same issue.
It goes back and forth from "couldn't open port" to telling me to "sign in to articulate 360 - click to launch your web browser to sign into Articulate 360."
I am able to log into the browser, but Articulate 360 still doesn't work.
I do not have the Desktop App.
Thanks!
Hi Lillian,
Thanks for sharing those images! Let's see if we can get this sorted out. If you are on a corporate network, ask your IT department to review the following article to allowlist the right endpoints for your Articulate 360 apps to work properly:
If you're not part of a corporate network, connect with our support team, and they'll be able to guide you on next steps to get this working!
had the same issue, checked this log file:
C:\Users\<username>\AppData\Local\Articulate\360\Logs\DesktopService_STABLE_20211125_061055.log
that was the error:
Exception while starting oidc callback listener: The format of the specified network name is invalid
found this: https://brakertech.com/iis-7-5-format-specified-network-name-invalid-iis-error-0x800704be/
deleted ip from IP listen list, put 0.0.0.0 instead = > resolved.
in my case, the problem happened because a couple of years ago I installed and configured some web server on my workstation, then deleted it and forgot.
but anyways, the bottom line is that the problem did not have anything to do with the firewall/service shortage/client version.