Remote Build Process is currently not working (x509)

#1
  1. My goal is: Build firmware using https://mongoose.cloud
  2. My actions are: mos build --platform esp32
  3. The result I see is:
Connecting to https://mongoose.cloud, user test
Uploading sources (53857 bytes)
Error: Post https://mongoose.cloud/api/fwbuild/2.14.0/build: x509: certificate has expired or is not yet valid
/go/src/github.com/mongoose-os/mos/mos/build_remote.go:297:
/go/src/github.com/mongoose-os/mos/mos/build.go:223:
/go/src/github.com/mongoose-os/mos/mos/build.go:166:
/go/src/github.com/mongoose-os/mos/mos/main.go:196: build failed
  1. My expectation & question is:
    The build process worked fine until just now. What’s the problem and how to work around it without local build?
1 Like
#2

same issue from 20 minutes

1 Like
#3

It appears the website certificate of mongoose cloud has expired. Can’t tell if this issue will be resolved rapidly or how long it will take…

2 Likes
#4

Same problem here until now…

#5

Fixed, thanks for reporting.

1 Like
#6

Seems that the certificate expired again

Connecting to https://mongoose.cloud, user test
Uploading sources (5500 bytes)
Error: Post https://mongoose.cloud/api/fwbuild/2.15.0/build: x509: certificate has expired or is not yet valid
/go/src/github.com/mongoose-os/mos/mos/build_remote.go:297: 
/go/src/github.com/mongoose-os/mos/mos/build.go:223: 
/go/src/github.com/mongoose-os/mos/mos/build.go:166: 
/go/src/github.com/mongoose-os/mos/mos/main.go:196: build failed

1 Like
#7

With the demo js app from the quick start guide, I’m getting connection refused:

Error: Post https://mongoose.cloud/api/fwbuild/2.15.0/build: dial tcp 88.198.37.49:443: connect: connection refused

Here is the complete past from mos:

$ mos build --platform esp32
Connecting to https://mongoose.cloud, user test
Uploading sources (2579 bytes)
Error: Post https://mongoose.cloud/api/fwbuild/2.15.0/build: dial tcp 88.198.37.49:443: connect: connection refused
/private/tmp/mos-20191002-29497-yt53zd/mos-b14a864da77d6f3b0b1ad591876b41cf06e70bab/src/cesanta.com/go/src/github.com/mongoose-os/mos/mos/build_remote.go:297: 
/private/tmp/mos-20191002-29497-yt53zd/mos-b14a864da77d6f3b0b1ad591876b41cf06e70bab/src/cesanta.com/go/src/github.com/mongoose-os/mos/mos/build.go:223: 
/private/tmp/mos-20191002-29497-yt53zd/mos-b14a864da77d6f3b0b1ad591876b41cf06e70bab/src/cesanta.com/go/src/github.com/mongoose-os/mos/mos/build.go:166: 
/private/tmp/mos-20191002-29497-yt53zd/mos-b14a864da77d6f3b0b1ad591876b41cf06e70bab/src/cesanta.com/go/src/github.com/mongoose-os/mos/mos/main.go:196: build failed
exit status 1
Command completed.

The server answers pings but it looks like the scp daemon on port 443 is down:

$ telnet 88.198.37.49 443

Trying 88.198.37.49...

telnet: connect to address 88.198.37.49: Connection refused

telnet: Unable to connect to remote host
#8

This is still happening after a bunch of hours, so I can’t imagine the problem is with the server. I have made sure my proxy is off, and I see I can connect via ssh. Any idea why mos is giving this error?

#9

The remote build is up now.

#10

Now I getting this error:

fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

It 's related to system restart?