Network connection lost error

Third Party Coronium
#21

Hi,

Yeah, I saw the ‘could not delete’, its on the fix list.

The major issue seems to have to do with the Lua code cache. Which was recently turned on by default (that was not the case before a month ago), so try:

sudo coronium-tools cacheoff

If that doesn’t work, try direct:

sed ‘/s/lua_code_cache on;/lua_code_cache off;/’ -i /usr/local/openresty/nginx/conf/nginx.conf

Reboot, try again. 

The AWS images are generally locked at a version, the Ubuntu installer will always be bleeding edge. Something to consider.

Most of this should be resolved soon with the next major release.

Cheers.

#22

I get this error on  sed ‘/s/lua_code_cache on;/lua_code_cache off;/’ -i /usr/local/openresty/nginx/conf/nginx.conf

sed: -e expression #1, char 5: extra characters after command

#23

Try it without the semi-colons.

Cheers

#24

same

#25

Hi,

I think I see the issue; me typing to hastily.  :unsure:

Try:

sudo sed ‘s/lua_code_cache on/lua_code_cache off/’ -i /usr/local/coronium/conf/coronium.conf

#26

yeah makes sense now, and it works :slight_smile:

#27

Hi Chris,

I seem to be having the same issue. I was finally able to get the HTTPS issue resolved but now having a new issue.

It seems to be attempting to call “http://” rather than “https://”. Note: app opened seems to be working, seems this is happening after calling mc:run. 

I have tried the steps in the thread above and verified I’m using the latest mod_coronium.lua file.

local mc = require( “mod_coronium” )

mc:init({ appId = globals.appId, apiKey = globals.apiKey, https = true })

mc:appOpened()

 

ERROR: network request failed: http://___my IP address here____/1/code/checkForUser [-1004: Could not connect to the server.]

error: Timed out

errorCode: -1

Runtime error

…

…(stack traceback details)…

…

result: Opened

 

Thanks,

Jeremiah