Remote Build Process is currently not working (x509)

  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

same issue from 20 minutes

1 Like

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

Same problem here until now…

Fixed, thanks for reporting.

1 Like

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

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

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?

The remote build is up now.

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?

Remote build is down again:

Connecting to https://mongoose.cloud, user test
Uploading sources (1177498 bytes)
Error: Post https://mongoose.cloud/api/fwbuild/2.17.0/build: x509: certificate has expired or is not yet valid
/src/go/src/github.com/mongoose-os/mos/cli/build_remote.go:298:
/src/go/src/github.com/mongoose-os/mos/cli/build.go:221:
/src/go/src/github.com/mongoose-os/mos/cli/build.go:164:
/src/go/src/github.com/mongoose-os/mos/cli/main.go:197: build failed

It would be great if this would not happen anymore and you would have your certificates updated automatically. By the way, it looks like your servers (mDash, Licensing) have been very busy for several weeks. So the licensing for Mongoose OS, which we use productively, was temporarily not available. I see this very critically, especially for production.

1 Like

it’s fixed now, thanks!

1 Like