{{ message }}
This repository was archived by the owner on Aug 15, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 15, 2022. It is now read-only.
Nothing loads on 8090 after installation #11529
Description
Steps to Reproduce (for bugs)
I have used docker for installation for koding and trying to access koding on 8090 for my server but nothing loads.
My docker containers:
3c0f6cde20ad koding/base "scripts/bootstrap-c…" 25 minutes ago Up 25 minutes 0.0.0.0:8090->8090/tcp koding_backend_1
105db55194b5 redis "docker-entrypoint.s…" 25 minutes ago Up 25 minutes 6379/tcp koding_redis_1
251c7b1bae42 rabbitmq:3-management "docker-entrypoint.s…" 25 minutes ago Up 25 minutes 4369/tcp, 5671-5672/tcp, 15671-15672/tcp, 25672/tcp koding_rabbitmq_1
aa669a621ca4 mongo:3.2.8 "/entrypoint.sh --no…" 25 minutes ago Up 25 minutes 27017/tcp koding_mongo_1
503b748b9b6e koding/base "scripts/bootstrap-c…" 25 minutes ago Up 25 minutes koding_client_1
15468113a86f koding/postgres "/usr/lib/postgresql…" 25 minutes ago Up 25 minutes 5432/tcp koding_postgres_1
46c21b63e952 countly/countly-server:16.06 "/sbin/my_init" 25 minutes ago Up 25 minutes 80/tcp koding_countly_1
328a0eaf140f koding/base "scripts/bootstrap-c…" 25 minutes ago Up 25 minutes koding_client-landing_1
docker logs -f 3c0f6cde20ad
/opt/koding /opt/koding
sudo ufw status
Status: active
To Action From
-- ------ ----
22/tcp ALLOW Anywhere
443/tcp ALLOW Anywhere
80/tcp ALLOW Anywhere
8090/tcp ALLOW Anywhere
22/tcp (v6) ALLOW Anywhere (v6)
443/tcp (v6) ALLOW Anywhere (v6)
80/tcp (v6) ALLOW Anywhere (v6)
8090/tcp (v6) ALLOW Anywhere (v6)
Context
Your Environment
- Version used:
- Environment name and version (e.g. Chrome 39, node.js 5.4):
- Operating System and version (desktop or mobile):
- Link to your project:
Activity
YonatanKra commentedon Apr 16, 2020
I get the same thing. Any solution to this?
killswitch-GUI commentedon Apr 22, 2020
Is this project dead?
schtinkafinga commentedon May 12, 2020
Looks like it is.
rvigneshw commentedon May 19, 2020
I'm also getting the same error.