webvm local deployment issues
https://github.com/leaningtech/webvm
When I follow the readme.md instructions I get a 403 on my nginx when I run
sudo nginx -c $HOME/GITHUB/webvm/nginx.conf
.
What am I missing?GitHub
GitHub - leaningtech/webvm: Virtual Machine for the Web
Virtual Machine for the Web. Contribute to leaningtech/webvm development by creating an account on GitHub.
11 Replies
That's difficult to sat without further information. 403 suggests there is a permission issue.
There should be a
nginx_error.log
that you can inspect to understand what is going wrong.
Also, what is the URL that is receiving a 403?
And make sure to have reviewed the local deployment instructions: https://github.com/leaningtech/webvm/tree/main?tab=readme-ov-file#local-deploymentYeah, I've followed those instructions. I changed index.html.
I am not totally sure which localhost port the webpage is served on. 8081 returns the nginx stuff.
Oh it should just be regular localhost shouldn't it?
http://localhost:8082/
is any of that info helpful?
I also chmod -R 777 the directory
The port is 8081
8081 returns the nginx stuffWhat do you mean exactly?
The root should point to the repository, so nginx is not being started correctly
Indeed, you are missing a parameter
-p $PWD
okay i will try that
now it's 403 on 8081
should I change root in the nginx.conf?
should there be a . in "/home/nyx/GITHUB/webvm/./index.html"?
alright well i got rid of that issue by changing around the root
but it's still a 403 error on everything
oh fuck i did it
i did a
sudo chmod o+x /home
since this is a vm
great
it worked out
and adding
to the nginx
now my only issue is that it isn't starting the debian_mini from releasesays CMD is not defined in browser tools
but it is uncommented
oh
i am supposed to comment out the top ones
aaaaaaaaaa
what the fuck is all this obfuscated js
https://cheerpxdemos.leaningtech.com/publicdeploy/20240501_137/cx.js
alright welp
this is literally impossible to debug
yeah I'm sure this 21k lines obfuscated JS is no big deal
Please check the network tab, that error is not the problem itself, just a symptom of a previous problem. If I have to make a guess the disk image url is not correct