is normal to get 502 bad gateway error??

[Flardryn 1]

hi

i hope u are all doing well.

just finished setting up my codius host but whenever i check codius.flardryn.com/version its giving me a 502 bad gateway error is that normal?

thanks in advance

[steffenmanden 256]

Most likely moneyd failing 

Edited June 16, 2018 by steffenmanden

[Soolan 1]

I'm getting the same error and my moneyd, codiusd, and nginx seem to be fine and active:

[root@codius1 bin]# systemctl status codiusd
● codiusd.service - Codiusd
   Loaded: loaded (/etc/systemd/system/codiusd.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2018-07-07 04:59:30 UTC; 10h ago
 Main PID: 2403 (npm)
   CGroup: /system.slice/codiusd.service
           ├─2403 npm
           └─2413 node src/index.js


[root@codius1 bin]# systemctl status moneyd-xrp
● moneyd-xrp.service - ILP provider using XRP payment channels
   Loaded: loaded (/usr/lib/moneyd-xrp/moneyd-xrp.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2018-07-07 04:49:24 UTC; 11h ago
 Main PID: 2256 (node)
   CGroup: /system.slice/moneyd-xrp.service
           └─2256 node /usr/lib/moneyd-xrp/moneyd/bin/moneyd.js xrp:start

[root@codius1 bin]# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

any idea what is wrong here?

Thank you.

Edited July 7, 2018 by Soolan

[MsKat141 26]

Did you ever solve the problem?  I'm getting a 502 Bad Gateway.

[Donkey 1,739]

9 hours ago, MsKat141 said:

Did you ever solve the problem?  I'm getting a 502 Bad Gateway.

When an incoming https request reaches Nginx at port 443, it is forwarded to port 3000 that the codiusd service is supposed to be listening to. In the event codiusd does not respond to the request, the 502 Bad Gateway condition occurs. This is usually because the codiusd service is not running properly. The key to solving this is to examine the moneyd and codiusd logs. You may want to pop over to https://gitter.im/codius/codius-chat for some real-time help.

[Donkey 1,739]

On 7/8/2018 at 1:50 AM, Soolan said:

I'm getting the same error and my moneyd, codiusd, and nginx seem to be fine and active:

[root@codius1 bin]# systemctl status codiusd
● codiusd.service - Codiusd
   Loaded: loaded (/etc/systemd/system/codiusd.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2018-07-07 04:59:30 UTC; 10h ago
 Main PID: 2403 (npm)
   CGroup: /system.slice/codiusd.service
           ├─2403 npm
           └─2413 node src/index.js


[root@codius1 bin]# systemctl status moneyd-xrp
● moneyd-xrp.service - ILP provider using XRP payment channels
   Loaded: loaded (/usr/lib/moneyd-xrp/moneyd-xrp.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2018-07-07 04:49:24 UTC; 11h ago
 Main PID: 2256 (node)
   CGroup: /system.slice/moneyd-xrp.service
           └─2256 node /usr/lib/moneyd-xrp/moneyd/bin/moneyd.js xrp:start

[root@codius1 bin]# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

any idea what is wrong here?

Thank you.

Do examine the moneyd and codiusd logs for error messages that can appear when the respective services are running. Even though "systemctl status" may show them as active, the services may be experiencing issues as they are running and these will produce error messages in the logs.

[CoinTrek 23]

On 6/16/2018 at 6:32 AM, Flardryn said:

hi

i hope u are all doing well.

just finished setting up my codius host but whenever i check codius.flardryn.com/version its giving me a 502 bad gateway error is that normal?

thanks in advance

502 error means that the edge server didn't give a response.  Are you in a redirect loop? Are your A records for your subdomain and wildcard subdomain DNS only? As in not through a CDN like cloudflare? 

[retryW 3,836]

Run the following:

netstat -tulpn

If you can't see an entry for 127.0.0.1:7768 then it's a moneyd issue. If you can't see an entry for 127.0.0.1:3000 but the previous entry exists, then it's a codiusd problem.  If you don't see 127.0.0.1:443 or 127.0.0.1:80 then it's a nginx problem.

 

Feel free to hit me or others up on https://gitter.im/codius/codius-chat for more help troubleshooting.