-
Notifications
You must be signed in to change notification settings - Fork 4
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
Demo link broken #16
Comments
Hi, Konrad.
We are able to access the online demo, which is publicly available. The
URL is correct: http://rsmsrv01.nci.org.au:8080/schimatos/
[image: image.png]
Perhaps the nature of the error comes from some network settings from your
end?
/$¡rm
Best regards,
Sergio J. Rodríguez M.
https://w3id.org/people/sergio
…On Wed, Dec 22, 2021 at 6:58 PM Konrad Höffner ***@***.***> wrote:
The link to http://schimatos.github.io/ in the readme file redirects to
http://rsmsrv01.nci.org.au:8080/schimatos/, which results in an "unable
to connect" error.
—
Reply to this email directly, view it on GitHub
<#16>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACLJPH5EOOUFMVJ4JBSME63USGALFANCNFSM5KR57LSQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
The error still persists on my university PC, however it works on my smartphone, so it seems as if this is due to the university firewall on this network, maybe the port 8080 is blocked. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The link to http://schimatos.github.io/ in the readme file redirects to http://rsmsrv01.nci.org.au:8080/schimatos/, which results in an "unable to connect" error. I am not using a VPN.
The text was updated successfully, but these errors were encountered: