Running online website through virtual box/ubuntu with godaddy domain - html

I really need help setting my website online with my GoDaddy domain. OK this is what I've done so far, please let me know if I did anything wrong, help will be much appreciated.
Ok so what I did was:
-Download virtualbox and downloaded Ubuntu Desktop (was I supposed to download the Server one?)
-I then bought my GoDaddy domain, example.com and pointed it to my home's router/ provided my IP address.
-So then I went to my routers config and allowed port 80 to my Ubuntu Desktop's IPV4/IP address (Starts with 10.0...
-I have Apache running on my Ubuntu/Linux Desktop, and made a file in the /etc/apache2/sites-available/example.com and provided the document root, server name, etc and then enabled the site using
sudo a2ensite example.com.
-I enabled bridge network on my Ubuntu and linux settings.
What else do I have to do? When I went to my router's configuration, it say's that my Ubuntu/virtual box is offline even though the Ubuntu does have internet. I'm able to access Facebook for example on my Ubuntu.
Is there anything else that I'm missing, please and please and please help. Would greatly appreciate it.

Maybe you will find this doc helpful http://catlingmindswipe.blogspot.ru/2012/06/how-to-virtualbox-networking-part-two.html But still, remember that the author of the article intends to create a sandbox, not a website for a regular use.
By the way, what is the operating system on your hardware box ?

Related

Encountered problem while integrating devstack - osm (open source mano)

I'm currently trying to develop a cloud in my pc using virtual box. The idea is that I have 2 virtual machines, one which devstack installed (all in one) and the other with osm mano. Right now both have everything installed. Hence, I can log in to mano via user and password 'admin' as well as to devstack.
Current properties:
VM1 (devstack): IP (enp0s8) -> 192.168.56.101
Login to 192.168.56.101 -> correct
VM2 (mano): IP (enp0s8) -> 192.168.56.105
Login to 192.168.56.105 -> correct
As some of you may guess, I have 2 network interfaces in every vm, the first one being NAT (enp0s3 with 10.0.2.15 IP) and the second one being Host Only (192.168.56.x according to virtual box).
Needless to say, I can ping from one virtual machine to another without any problem.
Now, in the past I've being using devstack (ubuntu 18.04) in order to play with it a little bit, learn how to deploy instances, create groups and so on. Indeed, I developed a topology with an instance as a router and nagios as the monitoring tool system. It worked and I learnt a lot!
Anyway, what I want in this case is starting from scratch (scratch meaning having downloaded mano and devstack but without going further). So here I am, trying to integrate OSM with Devstack, making use of osm-vim command as it is:
osm vim-create --name openstack-site --user admin --password my_openstack_password --auth_url http://192.168.56.101:5000/v3 --tenant admin --account_type openstack
In this case, my openrc file (downloaded from horizon) resulted in my auth_url being:
export OS_AUTH_URL=http://192.168.56.101:5000/v3
What I'm trying to get my head into is how it's possible that this doesn't work, as whenever I log-in to mano web interface (after osm-vim command) I go to VIM accounts and operational state equals to "error".
Any kind of help would be much appreciated, as I've being struggling for a week now.
Thanks in advance!
I had the same problem. At the beginning I thought It was a network problem, but finally I found out It was due to a SSL problem. The most easy solution is to put a specific flag to avoid the SSL verification until the developers fix it. "--config '{insecure: True}'"
I also encountered this problem when I finished installing OSM-10 and OpenStack-Ussuri for Ubuntu18.04 some days ago. I solved this problem by change the url "--auth_url http//:192.168.23.18:5000/v3" to "-- auth_url http//:controller:5000/v3" and put "192.168.23.18 controller" in the ro container "/etc/hosts". The "controller" here is the host name where you install your openstack and which is used is your keystone authentication urls. Maybe you also have solved this problem but this problem is so troublesome and I hope more people do not be annoyed at this~

Can't log in to an app running on LocalHost - no network activity?

I'm working on an app with a team. They are able to log in fine when running it on their local servers, however when I try to do so I get 'Invalide username / password' and no network activity or console errors in dev tools.
I have no idea why this could be, we're working on the exact same code - clearly it's something on my machine.
Has anyone come across anything like this before?
(Have tried other browsers and still nothing).
Maybe you need to check your server instalation on your machine.
For example, if you are using XAMPP to manage your Apache maybe there is some configuration that was set in the wrong way.
My advice is, save your code and re-install your server, pay attention to all configuration details and see if the problem is solved.

Google Chrome remote debugging local domain

I'm developing a website on my local machine using myblog.local as a custom domain for that, I have an apache VirtualHost and the name registered on the hosts file of my mac. The thing is when I try to use chrome remote debugging on my USB connected device using myblog.local as an address pushed using the chrome://inspect tool.
I always a not found error.
My question is, do I need to do something extra in order to remotely debug a custom domain registered on my Mac?
Check out Map to custom local domains.
I got it set up once to work with custom local domains, but it took a bit of experimenting. I definitely needed a proxy server to get it working.
I had exactly the same problem on a PC. I followed #Kayce Basques' Map to custom local domains guide and after some perseverance everything is now working.
Kayce's guide requires a proxy server, I've included my working configuration for the Squid open source and free proxy server below.
Squid installation was easy, I just downloaded and installed a pre-compiled Windows binary file and the server appeared in my Windows system tray. It should hopefully be equally simple for OSX and Linux platforms.
All configuration is done inside a squid.conf file accessible from the Squid menu. I followed this simple guide for a Reverse Proxy. Whilst I included everything in that guide I believe the following line is the critical one to get everything working.
cache_peer 192.168.0.2 parent 80 0 no-query proxy-only originserver
In the above line 192.168.0.2 is my PC's internal IP address and 80 is my Apache virtual host port number defined in my Apache Virtual Hosts file. There's another helpful guide here but that guide omits the originserver option and didn't work on my machine though otherwise helpful.
It seems you do need to be connected by USB cable for this to work so I don't quite understand #asolenzal's comment above. Also each time I changed the configuration I ran Path/to/squid.exe -k reconfigure -n Squid in a command window to reload Squid. You can find that command here.

Can't Access localhost or 127.0.0.1 in wamp

I was using wamp 2.1a for my wordpress blog and a website. It was working fine. Then I caught a google redirect virus. I tried hard to get rid of it, finally i fixed it. Then, suddenly my wamp server stopped working, I mean both the services were running but when I opened localhost or 127.0.0.1, it just kept loading, and went on forever till I closed the browser's tab. Then I upgraded to wamp 2.2a and the problem is still there.
I've also checked the hosts file, tried to change the port to 8080 for apache, but it didn't help. I do not have skype (and never used it) so there's no port 80 conflict. When I restart the services, the apache service starts but the mysql service doesn't. When I click wamp tray menu, click on the remove service for mysql, a message box appears saying - mysqld.exe has stopped working. The only option I have there is close program.
I can't access my blog so I can't so any testing. Please tell me if this happened to you or if you have a solution to this. Any help is appreciated.
Did you try different web browser? I guess it is browser problem, clear your browser cache, might solve your problem.
I have found the following solution in another post here (from Sergiu Butnarasu) which worked for me.
Modify the apache HTTPD.CONF file. Change "Listen 80" to "Listen 0.0.0.0:80 http://forum.wampserver.com/read.php?2,93143

EC2 Server troubleshooting

I have an instance running that points to an elastic IP. I also have the A record on GoDaddy pointing to that same elastic IP. I created a key, installed php, httpd, etc... through putty, gave ec2-user chown permissions in var/www/html and sub directories and plopped a simple index.html in that folder.
The problem is, I still get the 404 - so the site is completely unresponsive. I can nav into the site with WinSCP fine and the directories are all there. Is there something I am completely overlooking that is just an oversight on my part or do I have deeper issues?
Much thanks!
EDIT:
I did a simple service httpd status to check if Apache is running, and sure enough it is.
If you recently updated the dns on GoDaddy it may just be that you have to wait for the dns to propagate to the right nameservers. Have you checked that you are getting a 404 from the right ip address?