Failure during connecting: wss://lit.luvit.io/

[Geoff Bourne]

I am seeing the following failure in two builds now right at the start of the "including dependency" step:

connecting: wss://lit.luvit.io/
fail: [string "bundle:libs/rdb.lua"]:44: Error verifying peer: ok
stack traceback:
        [C]: in function 'assert'
        [string "bundle:libs/rdb.lua"]:44: in function 'connectRemote'
        [string "bundle:libs/rdb.lua"]:87: in function 'connect'
        [string "bundle:libs/rdb.lua"]:121: in function 'match'
        [string "bundle:libs/calculate-deps.lua"]:72: in function 'addDep'
        [string "bundle:libs/calculate-deps.lua"]:49: in function 'processDeps'
        [string "bundle:libs/calculate-deps.lua"]:92: in function 'calculateDeps'
        [string "bundle:libs/core.lua"]:421: in function 'make'
        [string "bundle:commands/make.lua"]:11: in function <[string "bundle:commands/make.lua"]:1>
        [string "bundle:main.lua"]:52: in function <[string "bundle:main.lua"]:39>
        [C]: in function 'xpcall'
        [string "bundle:main.lua"]:39: in function <[string "bundle:main.lua"]:31>

[Tim Caswell]

I'll fix it.  It looks like my lets encrypt cert stopped auto-updating.

--
You received this message because you are subscribed to the Google Groups "luvit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to luvit+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tim Caswell]

Ok, should be fixed now.  What had happened was I had moved `luvit.io` to Heroku so it would stay up automatically and the let's encrypt script was trying to renew both and failing since the dns had changed for luvit.io.

[Geoff Bourne]

Thanks, yes, that has fixed it.