[GH-ISSUE #64] Connection refused #47

Closed
opened 2026-02-26 02:31:54 +03:00 by kerem · 10 comments
Owner

Originally created by @psagat on GitHub (Dec 15, 2015).
Original GitHub issue: https://github.com/koel/koel/issues/64

Would like to try your software but can't seem to get past the connection refused.

apache2 2442 root 4u IPv6 20261 0t0 TCP *:80 (LISTEN)
apache2 2445 www-data 4u IPv6 20261 0t0 TCP *:80 (LISTEN)
apache2 2446 www-data 4u IPv6 20261 0t0 TCP *:80 (LISTEN)
apache2 2447 www-data 4u IPv6 20261 0t0 TCP *:80 (LISTEN)
apache2 2448 www-data 4u IPv6 20261 0t0 TCP *:80 (LISTEN)
apache2 2449 www-data 4u IPv6 20261 0t0 TCP *:80 (LISTEN)
php5 2521 root 6u IPv4 20355 0t0 TCP 127.0.0.1:8000 (LISTEN)

Do I need to do something with apace? I attempted the install using a ubuntu 15 server lamp stack.

Originally created by @psagat on GitHub (Dec 15, 2015). Original GitHub issue: https://github.com/koel/koel/issues/64 Would like to try your software but can't seem to get past the connection refused. apache2 2442 root 4u IPv6 20261 0t0 TCP *:80 (LISTEN) apache2 2445 www-data 4u IPv6 20261 0t0 TCP *:80 (LISTEN) apache2 2446 www-data 4u IPv6 20261 0t0 TCP *:80 (LISTEN) apache2 2447 www-data 4u IPv6 20261 0t0 TCP *:80 (LISTEN) apache2 2448 www-data 4u IPv6 20261 0t0 TCP *:80 (LISTEN) apache2 2449 www-data 4u IPv6 20261 0t0 TCP *:80 (LISTEN) php5 2521 root 6u IPv4 20355 0t0 TCP 127.0.0.1:8000 (LISTEN) Do I need to do something with apace? I attempted the install using a ubuntu 15 server lamp stack.
kerem closed this issue 2026-02-26 02:31:54 +03:00
Author
Owner

@psagat commented on GitHub (Dec 15, 2015):

Also. Your install instructions are not that verbose. Do I need to do anything on a fresh box other than these? I have a base mysql database with homestead created as the database, as well as apache and can access the index.html. Does it matter where I drop koel folder?

git clone https://github.com/phanan/koel && cd koel
npm install
composer install
vi .env # Fill in database info and initial admin account
php artisan init
php artisan serve

<!-- gh-comment-id:164919321 --> @psagat commented on GitHub (Dec 15, 2015): Also. Your install instructions are not that verbose. Do I need to do anything on a fresh box other than these? I have a base mysql database with homestead created as the database, as well as apache and can access the index.html. Does it matter where I drop koel folder? git clone https://github.com/phanan/koel && cd koel npm install composer install vi .env # Fill in database info and initial admin account php artisan init php artisan serve
Author
Owner

@phanan commented on GitHub (Dec 16, 2015):

Koel isn't different than any other PHP websites – if you can get them up and running, you can get Koel.

I have a base mysql database with homestead created as the database, as well as apache and can access the index.html. Does it matter where I drop koel folder?

I'd say you drop koel's content where the index.html is, i.e. index.html and index.php should be at the same level.

<!-- gh-comment-id:164970459 --> @phanan commented on GitHub (Dec 16, 2015): Koel isn't different than any other PHP websites – if you can get them up and running, you can get Koel. > I have a base mysql database with homestead created as the database, as well as apache and can access the index.html. Does it matter where I drop koel folder? I'd say you drop koel's _content_ where the index.html is, i.e. index.html and index.php should be at the same level.
Author
Owner

@psagat commented on GitHub (Dec 16, 2015):

Yea not really familiar with web dev, system engineer myself. So laravel and bower etc are foreign to me.

Do you have a more detailed guide on standing up a fresh LAMP stack and getting your app to work? As of right now, I can access the login page, but when I hit submit I just get this back:

The requested URL /login was not found on this server.

<!-- gh-comment-id:164972325 --> @psagat commented on GitHub (Dec 16, 2015): Yea not really familiar with web dev, system engineer myself. So laravel and bower etc are foreign to me. Do you have a more detailed guide on standing up a fresh LAMP stack and getting your app to work? As of right now, I can access the login page, but when I hit submit I just get this back: The requested URL /login was not found on this server.
Author
Owner

@phanan commented on GitHub (Dec 16, 2015):

Do you have a more detailed guide on standing up a fresh LAMP stack and getting your app to work?

Unfortunately not, and I don't think it's in Koel's scope either.

The requested URL /login was not found on this server.

I'm blind guessing here, but looks like you need to enable mod_rewrite.

<!-- gh-comment-id:164973322 --> @phanan commented on GitHub (Dec 16, 2015): > Do you have a more detailed guide on standing up a fresh LAMP stack and getting your app to work? Unfortunately not, and I don't think it's in Koel's scope either. > The requested URL /login was not found on this server. I'm blind guessing here, but looks like you need to enable `mod_rewrite`.
Author
Owner

@phanan commented on GitHub (Dec 16, 2015):

I'm going to close this issue to clean up the list. Feel free to continue discussing here though.

<!-- gh-comment-id:164974186 --> @phanan commented on GitHub (Dec 16, 2015): I'm going to close this issue to clean up the list. Feel free to continue discussing here though.
Author
Owner

@psagat commented on GitHub (Dec 16, 2015):

I guess what I am asking then, is that I have the lamp stack setup. But the wiki instructions arent very clear on certain steps:

When you say:
cd PUBLIC_DIR

Do you mean put the koel dir inside a public site for apache etc?
And

bower install and gulp should have been executed post-installation

If for some reason they haven't, just manually execute them

bower install && gulp --production

How do we know if bower or gulp ran?

Do we run

/var/www/koel/node_modules/bower/bin and gulp.js ?

<!-- gh-comment-id:164975107 --> @psagat commented on GitHub (Dec 16, 2015): I guess what I am asking then, is that I have the lamp stack setup. But the wiki instructions arent very clear on certain steps: When you say: cd PUBLIC_DIR Do you mean put the koel dir inside a public site for apache etc? And # bower install and gulp should have been executed post-installation # If for some reason they haven't, just manually execute them # bower install && gulp --production How do we know if bower or gulp ran? Do we run /var/www/koel/node_modules/bower/bin and gulp.js ?
Author
Owner

@psagat commented on GitHub (Dec 16, 2015):

And it looks like

php5 2521 root 6u IPv4 20355 0t0 TCP 127.0.0.1:8000 (LISTEN)

I can wget and I get back a response so it appears to be only binding on the loop back which means I cant access it outside the box. How do we have it bind to something other than the loopback?

<!-- gh-comment-id:164978140 --> @psagat commented on GitHub (Dec 16, 2015): And it looks like php5 2521 root 6u IPv4 20355 0t0 TCP 127.0.0.1:8000 (LISTEN) I can wget and I get back a response so it appears to be only binding on the loop back which means I cant access it outside the box. How do we have it bind to something other than the loopback?
Author
Owner

@psagat commented on GitHub (Dec 16, 2015):

Alright.

I manually ran:

/usr/bin/php5 -S 192.168.1.46:8000 /var/www/koel/server.php

which allowed me to get the site going. But how do I change it so I can use the php artisan serve to bind on that ip?

<!-- gh-comment-id:164979442 --> @psagat commented on GitHub (Dec 16, 2015): Alright. I manually ran: /usr/bin/php5 -S 192.168.1.46:8000 /var/www/koel/server.php which allowed me to get the site going. But how do I change it so I can use the php artisan serve to bind on that ip?
Author
Owner

@phanan commented on GitHub (Dec 16, 2015):

php artisan serve is only meant for development purpose. For production, you'll need to configure a virtual host for Apache.

<!-- gh-comment-id:164981346 --> @phanan commented on GitHub (Dec 16, 2015): `php artisan serve` is only meant for development purpose. For production, you'll need to configure a virtual host for Apache.
Author
Owner

@phanan commented on GitHub (Dec 16, 2015):

Do you mean put the koel dir inside a public site for apache etc?

Yes.

How do we know if bower or gulp ran?

By looking at the console 😄

Do we run

/var/www/koel/node_modules/bower/bin and gulp.js ?

You don't need to, but there's no harm either.

<!-- gh-comment-id:164982674 --> @phanan commented on GitHub (Dec 16, 2015): > Do you mean put the koel dir inside a public site for apache etc? Yes. > How do we know if bower or gulp ran? By looking at the console :smile: > Do we run > > /var/www/koel/node_modules/bower/bin and gulp.js ? You don't need to, but there's no harm either.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#47
No description provided.