Picture of James Bevelander
Authoring Tool installation issue
by James Bevelander - Monday, 31 October 2016, 3:01 AM
 

Hi Guys! 

After spending half the day grappling with Command Prompt and failed attempts to get "vagrant up" to work, I finally got it working and providing the localhost details.

I thought I was only seconds away from jumping onto the authoring tool and having a play.

No such luck! Whenever I type http://localhost:5000 into chrome or Firefox I get the screen below but no prompt to login.....what am I missing. How can I jump onto the authoring tool from here?

Picture of James Bevelander
Re: Authoring Tool installation issue
by James Bevelander - Monday, 31 October 2016, 3:47 AM
 

sorry, for context .......this is the vagrant up command prompt output

 

 

c:\Program Files\adapt_authoring-master>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty32' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 5000 (guest) => 5000 (host) (adapter 1)
default: 5858 (guest) => 5858 (host) (adapter 1)
default: 27017 (guest) => 27027 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version o
f
default: VirtualBox! In most cases this is fine, but in rare cases it can
default: prevent things such as shared folders from working properly. If you
see
default: shared folder errors, please make sure the guest additions within t
he
default: virtual machine match the version of VirtualBox you have installed
on
default: your host and reload your VM.
default:
default: Guest Additions Version: 4.3.36
default: VirtualBox Version: 5.1
==> default: Mounting shared folders...
default: /vagrant => C:/Program Files/adapt_authoring-master
==> default: Machine already provisioned. Run `vagrant provision` or use the `--
provision`
==> default: flag to force provisioning. Provisioners marked to run always will
still run.
==> default: Running provisioner: shell...
default: Running: C:/Users/James/AppData/Local/Temp/vagrant-shell20161031-68
72-61jt2u.sh
==> default: [PM2] Spawning PM2 daemon with pm2_home=/home/vagrant/.pm2
==> default: [PM2] PM2 Successfully daemonized
==> default: [PM2][WARN] Applications adapt not running, starting...
==> default: [PM2] App [adapt] launched (1 instances)
==> default: ┌──────────┬────┬──────┬──────┬────────┬─────────┬────────┬─────┬──
─────────┬──────────┐
==> default: │ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ m
em │ watching │
==> default: ├──────────┼────┼──────┼──────┼────────┼─────────┼────────┼─────┼──
─────────┼──────────┤
==> default: │ adapt │ 0 │ fork │ 1380 │ online │ 0 │ 0s │ 3% │ 1
2.9 MB │ enabled │
==> default: └──────────┴────┴──────┴──────┴────────┴─────────┴────────┴─────┴──
─────────┴──────────┘
==> default: Use `pm2 show <id|name>` to get more details about an app
==> default: Running provisioner: shell...
default: Running: C:/Users/James/AppData/Local/Temp/vagrant-shell20161031-68
72-1uap5z3.sh
==> default: stdin: is not a tty
==> default: ---------------------------------------------------------
==> default: Adapt Authoring Tool is running on: http://localhost:5000
==> default: username: admin
==> default: password: password
==> default: ---------------------------------------------------------

c:\Program Files\adapt_authoring-master>node -v
'node' is not recognized as an internal or external command,
operable program or batch file.

c:\Program Files\adapt_authoring-master>vagrant halt
==> default: Attempting graceful shutdown of VM...

c:\Program Files\adapt_authoring-master>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty32' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 5000 (guest) => 5000 (host) (adapter 1)
default: 5858 (guest) => 5858 (host) (adapter 1)
default: 27017 (guest) => 27027 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version o
f
default: VirtualBox! In most cases this is fine, but in rare cases it can
default: prevent things such as shared folders from working properly. If you
see
default: shared folder errors, please make sure the guest additions within t
he
default: virtual machine match the version of VirtualBox you have installed
on
default: your host and reload your VM.
default:
default: Guest Additions Version: 4.3.36
default: VirtualBox Version: 5.1
==> default: Mounting shared folders...
default: /vagrant => C:/Program Files/adapt_authoring-master
==> default: Machine already provisioned. Run `vagrant provision` or use the `--
provision`
==> default: flag to force provisioning. Provisioners marked to run always will
still run.
==> default: Running provisioner: shell...
default: Running: C:/Users/James/AppData/Local/Temp/vagrant-shell20161031-41
56-mqgz6w.sh
==> default: [PM2] Spawning PM2 daemon with pm2_home=/home/vagrant/.pm2
==> default: [PM2] PM2 Successfully daemonized
==> default: [PM2][WARN] Applications adapt not running, starting...
==> default: [PM2] App [adapt] launched (1 instances)
==> default: ┌──────────┬────┬──────┬──────┬────────┬─────────┬────────┬─────┬──
─────────┬──────────┐
==> default: │ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ m
em │ watching │
==> default: ├──────────┼────┼──────┼──────┼────────┼─────────┼────────┼─────┼──
─────────┼──────────┤
==> default: │ adapt │ 0 │ fork │ 1375 │ online │ 0 │ 0s │ 75% │ 1
2.3 MB │ enabled │
==> default: └──────────┴────┴──────┴──────┴────────┴─────────┴────────┴─────┴──
─────────┴──────────┘
==> default: Use `pm2 show <id|name>` to get more details about an app
==> default: Running provisioner: shell...
default: Running: C:/Users/James/AppData/Local/Temp/vagrant-shell20161031-41
56-1pfffno.sh
==> default: stdin: is not a tty
==> default: ---------------------------------------------------------
==> default: Adapt Authoring Tool is running on: http://localhost:5000
==> default: username: admin
==> default: password: password
==> default: ---------------------------------------------------------

Picture of Gary Ritchie
Re: Authoring Tool installation issue
by Gary Ritchie - Monday, 31 October 2016, 1:39 PM
 
c:\Program Files\adapt_authoring-master>node -v
'node' is not recognized as an internal or external command,

Try vagrant provision (on the host) again to force provisioning since it looks like node didn't get installed properly during the initial `vagrant up`.

This might help with the warnings about guest additions (run on the host):

vagrant plugin install vagrant-vbguest

Picture of James Bevelander
Re: Authoring Tool installation issue
by James Bevelander - Wednesday, 2 November 2016, 8:29 PM
 

thanks Gary.....FYI I ended up getting it to work by taking adapt_authoring-master out of C://program files and just putting it in C://

Obviously it being in a folder that requires permissions is a bad thing! I'm a bit of a noob so this is probably common sense to most people but it was doing my head in for days.

luckily I stumbled across this tutorial which highlighted that it shouldn't be in a folder with permissions.

https://www.youtube.com/watch?v=qQNkecFdO_Q