Failed to load resource: the server responded with a status of 404 (Not Found)

[ghost]

Hi, I am getting this in the Chrome Console:

Failed to load resource: the server responded with a status of 404 (Not Found)
http://localhost:8080/candy/candy.min.js Failed to load resource: the server responded with a status of 404 (Not Found)
(index):15 Uncaught ReferenceError: Candy is not defined

Browser screenshot:

Any idea? Thanks.

[mweibel]

Hi,

could you tell me what's inside /usr/share/nginx/html/candy?

[ghost]

Hi,

vagrant@vagrant-ubuntu-trusty-64:/usr/share/nginx/html/candy$ ls
CONTRIBUTING.md CREDITS.md Gruntfile.js LICENSE README.md Vagrantfile bower.json candy devbox example package.json res setup.sh src tests vendor_libs

[mweibel]

Ah, yeah.. The dev branch doesn't contain candy.bundle.js/candy.min.js anymore.
Could you try if it works with the changes in PR #3?

You should be able to run vagrant provision again in order to verify.

[ghost]

This patch works for me (now I get the Nickname login page), but after login I get "Status: 2" error (see screenshot below).

diff --git a/provisioning.sh b/provisioning.sh
index a75cc75..7daa9b7 100644
--- a/provisioning.sh
+++ b/provisioning.sh
@@ -40,14 +40,13 @@ ln -fs /vagrant/candy-index.html /usr/share/nginx/html/index.html
 sudo add-apt-repository ppa:chris-lea/node.js
 sudo apt-get update
 sudo apt-get install -y nodejs git
-npm install -g grunt-cli
-npm install -g bower
-
-cd /vagrant
-su -u vagrant npm install
-su -u vagrant bower install
+sudo npm install -g grunt-cli
+sudo npm install -g bower

 cd /vagrant/candy
+sudo npm install
+bower install
+
 grunt build

 #

[mweibel]

Is prosody running? what happens if you open http://localhost:5280/xmpp-websocket?

[ghost]

Prosody is running:

vagrant@vagrant-ubuntu-trusty-64:~$ ps aux | grep prosody
prosody   1130  0.0  0.7  48312  3712 ?        S    06:35   0:00 /usr/bin/lua5.1 /usr/bin/prosody

When I go to that url (inside the virtual machine and from the host) I get:

404 Not Found

Whatever you were looking for is not here. Keep looking.

EDIT: When I test http://localhost:5280/http-bind it says:

It works! Now point your BOSH client to this URL to connect to Prosody.

For more information see Prosody: Setting up BOSH.

[mweibel]

can you reprovision using the updated patch? mod_websockets is now shipped with prosody by default, no need to download it

[mweibel]

nevermind, doesn't work ;/ need to investigate later...

[humitos]

I'm having the same problem here. I get: "Status: 2" after login. I'm using prosody 0.8.2 (from a RaspberryPi)

[bogdanr]

I am using Prosody 0.9.10 and I get this:

[Strophe][ERROR]: BOSH-Connection failed: undefined
Candy.Core</a.init/b.log(a=3, c="BOSH-Connection failed: undefined")candy.min.js (line 1)
f.error(a="BOSH-Connection failed: undefined")libs.min.js (line 1)
Strophe.Bosh.prototype._connect_cb(a=Object { type="object"})libs.min.js (line 2)
f.Connection.prototype._connect_cb(a=Object { type="object"}, b=undefined, c=undefined)libs.min.js (line 1)
Strophe.Bosh.prototype._onRequestStateChange(a=Object { type="object"}, b=Object { type="object"})libs.min.js (line 2)