ozoneplatform.org down?

127 views
Skip to first unread message

Darren Lock

unread,
Feb 22, 2017, 12:17:16 PM2/22/17
to ozoneplatform-users
I am trying to install the ozp docker as per the instructions on:


But when I run “docker-compose up”  it fails with a timeout to ozoneplatform.org when trying to pull the ozp-auth package.

kdrumm...@gmail.com

unread,
Feb 22, 2017, 3:55:14 PM2/22/17
to ozoneplatform-users
Hi Darren,

Yes, ozoneplatform.org is currently down.  We are working to restore it.

Thanks,
Kyle

kdrumm...@gmail.com

unread,
Feb 24, 2017, 9:56:45 AM2/24/17
to ozoneplatform-users
ozoneplatform.org is back up.  Sorry for the inconvenience.  Please let us know if you notice any further issues.

bhain...@gmail.com

unread,
Jul 1, 2017, 8:58:16 AM7/1/17
to ozoneplatform-users
Darren,

Did this ever work for you?  I also experienced an issue with using the docker container.


On Wednesday, February 22, 2017 at 12:17:16 PM UTC-5, Darren Lock wrote:

kdrumm...@gmail.com

unread,
Jul 3, 2017, 7:14:24 AM7/3/17
to ozoneplatform-users, bhain...@gmail.com
What issue are you having?

bhain...@gmail.com

unread,
Jul 3, 2017, 8:45:43 AM7/3/17
to ozoneplatform-users, bhain...@gmail.com
This is the error message I get when I try docker-compose up:

C:\ozp-test\ozp-docker-runner>docker-compose up
Creating network "ozpdockerrunner_default" with the default driver
ERROR: Get https://ozoneplatform.org:8443/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Darren Lock

unread,
Jul 3, 2017, 8:54:28 AM7/3/17
to ozoneplatform-users, bhain...@gmail.com
Yes, once the server was back up all worked OK for me.

bhain...@gmail.com

unread,
Jul 3, 2017, 2:21:31 PM7/3/17
to ozoneplatform-users, bhain...@gmail.com
Darren, were you on Windows or Linux?

Kyle, do you know if the server is up now?  I'd really like to get it working this way if I can.

Darren Lock

unread,
Jul 3, 2017, 2:40:26 PM7/3/17
to ozoneplat...@googlegroups.com
Centos 7 and then later Windows 10

--
You received this message because you are subscribed to a topic in the Google Groups "ozoneplatform-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ozoneplatform-users/L6hflWO4LHU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ozoneplatform-users+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

tdpa...@gmail.com

unread,
Jul 3, 2017, 4:00:09 PM7/3/17
to ozoneplatform-users, bhain...@gmail.com
ozoneplatform.org is up and I've verified that the ozp-docker-runner is working correctly. From your output, it looks like your connection to the Internet is blocking outbound port 8443. Can you check both of these URLs and see if you're able to connect:
The first one is on the standard port 80, and the second is the same thing on port 8443.

bhain...@gmail.com

unread,
Jul 3, 2017, 5:14:08 PM7/3/17
to ozoneplatform-users, bhain...@gmail.com, tdpa...@gmail.com
I was able to ping those sites, and I definitely got further this time.  I think that part of the problem was on my side.

But here's the new error I'm getting:
.
.
.
Creating ozp-cache ...
Creating ozp-auth ...
Creating ozp-cache
Creating ozp-auth ... done
Creating ozp-backend ...
Creating ozp-backend ... error

ERROR: for ozp-backend  Cannot create container for service ozp-backend: Drive has not been shared

ERROR: for ozp-backend  Cannot create container for service ozp-backend: Drive has not been shared
ERROR: Encountered errors while bringing up the project.

Any help would be appreciated.

tdpa...@gmail.com

unread,
Jul 5, 2017, 11:15:40 AM7/5/17
to ozoneplatform-users, bhain...@gmail.com, tdpa...@gmail.com
What OS are you using, and what is the output of "docker --version" and "docker-compose --version" on your system?

bhain...@gmail.com

unread,
Jul 7, 2017, 9:30:33 AM7/7/17
to ozoneplatform-users, bhain...@gmail.com, tdpa...@gmail.com
I've tried it on Windows 7 and WIndows 10.  On Windows 7, it's running docker toolbox, but the Docker version is 17.05ce, build 89658be and the docker compose version is 1.13.0, build 1719ceb8.

On Windows 10, it's running docker and the version is 17.06.0-ce, build 02c1d87 and the docker-compose version is 1.14.0, build c7bdf9e3.

tdpa...@gmail.com

unread,
Jul 7, 2017, 12:22:22 PM7/7/17
to ozoneplatform-users, bhain...@gmail.com, tdpa...@gmail.com
Can you try it from Linux (or a Linux VM)? We don't support running the containers from Windows, and the error message you got seems to be related to Docker on Windows.

Tom

E Haines

unread,
Jul 7, 2017, 2:40:02 PM7/7/17
to ozoneplat...@googlegroups.com, tdpa...@gmail.com
I'll try that.  Thanks!

--

bhain...@gmail.com

unread,
Jul 7, 2017, 2:40:44 PM7/7/17
to ozoneplatform-users, bhain...@gmail.com, tdpa...@gmail.com
I'll try that.  Thanks!

bhain...@gmail.com

unread,
Jul 8, 2017, 7:46:13 AM7/8/17
to ozoneplatform-users, tdpa...@gmail.com, bhain...@gmail.com
That was the problem!  I tried it on a Linux VM and it worked!  Thanks for your help!

ccl...@isenpai.com

unread,
May 23, 2018, 1:42:39 PM5/23/18
to ozoneplatform-users
I hate to fire up an old(ish) thread, but this is failing for me due to an expired certificate.  Is the site still maintained?

Status: Downloaded newer image for redis:3.2-alpine

Pulling ozp-auth (ozoneplatform.org:8443/ozp-auth:latest)... ERROR: Get https://ozoneplatform.org:8443/v2/: x509: certificate has expired or is not yet valid


I've tried it on Ubuntu and CentOS7



On Wednesday, February 22, 2017 at 12:17:16 PM UTC-5, Darren Lock wrote:

luke.ste...@gmail.com

unread,
May 24, 2018, 8:27:16 AM5/24/18
to ozoneplatform-users
Same on Mac OS today

$ docker-compose up

Pulling ozp-auth (ozoneplatform.org:8443/ozp-auth:latest)...

ERROR: Get https://ozoneplatform.org:8443/v2/: x509: certificate has expired or is not yet valid


I'm not behind any corporate firewalls or proxies.

ccl...@isenpai.com

unread,
May 24, 2018, 8:36:25 AM5/24/18
to ozoneplat...@googlegroups.com
It's definitely due to an expired cert.

I received an e-mail from NextCentury regarding the site and he said that they are working on a solution and he should have more of an idea next week of when it will be resolved.

We shall see what happens.

luke.ste...@gmail.com

unread,
May 24, 2018, 8:51:40 AM5/24/18
to ozoneplatform-users
Add

ozoneplatform.org:8443/v2/


to your preferences / insecure registries in docker.

On Thursday, 24 May 2018 03:42:39 UTC+10, ccl...@isenpai.com wrote:

Luke Kay

unread,
May 24, 2018, 8:52:20 AM5/24/18
to ozoneplat...@googlegroups.com

to your preferences / insecure registries in docker.
On Thursday, 24 May 2018 03:42:39 UTC+10, ccl...@isenpai.com wrote:
I hate to fire up an old(ish) thread, but this is failing for me due to an expired certificate.  Is the site still maintained?

Status: Downloaded newer image for redis:3.2-alpine

Pulling ozp-auth (ozoneplatform.org:8443/ozp-auth:latest)... ERROR: Get https://ozoneplatform.org:8443/v2/: x509: certificate has expired or is not yet valid


I've tried it on Ubuntu and CentOS7



On Wednesday, February 22, 2017 at 12:17:16 PM UTC-5, Darren Lock wrote:
I am trying to install the ozp docker as per the instructions on:


But when I run “docker-compose up”  it fails with a timeout to ozoneplatform.org when trying to pull the ozp-auth package.


--
- This e-mail and any attachments are confidential and may be privileged and/or company-proprietary. If you are not the intended recipient, please notify iSenpai, LLC immediately - by replying to this message - and destroy all copies of this message and any attachments. Thank you.
Message has been deleted

ccl...@isenpai.com

unread,
May 24, 2018, 12:21:52 PM5/24/18
to ozoneplat...@googlegroups.com
This worked for me.

For future readers, this is what I did as su (sudo didn't work on the EC2 instance):
su -



cd
/etc/docker

vi daemon
.json

{

     
"insecure-registries" : [

         
"https://ozoneplatform.org:8443"

     
]

}

exit



ccl...@isenpai.com

unread,
Jun 6, 2018, 8:29:38 AM6/6/18
to ozoneplat...@googlegroups.com
I just received an e-mail from NextCentury stating that the cert has been successfully updated.

Reply all
Reply to author
Forward
0 new messages