I have just begun working with flask and deploying a website to Heroku. Suddenly I realized that my apache2 server on the same server is not accessible beyond localhost anymore even though it had been accessible within my local network prior to this. Has flask been known to interfere with apache?
Related
I've completed programming my site with Ratchet locally and I usually run the server file by
php server.php
now Idk how to actually make it work on the host?
I have Vps too but cant even fighre out how to connect it with the host , etc? what is the idea actually
In your VPS you should install a webserver for example Apache or Nginx and config them to serve requests, but actually is far more easier to use preconfigured servers with server software management like Cpanel or directadmin that most of web hostings offer now days,
Then copy local files to remote server and adjust a database in server using a ftp client and config php web server settings, in general your webserver should point to your index.php file and thats it. You can learn other settings by exploring directadmin or Cpanel...
We cloned the servers, upgraded to a newer version of the OS (Windows 2012) which is compatible with the web app. However, when we placed those servers in production, only the one with the load balancer was being accessible through the IP. The other 4 were not because the load balancer was trying to redirect traffic to the local IP instead of the public ones. I don't know if this is information enough, but we can't seem to find the issue since the config of the web app is the same and the IIS didn't seem to have issues. Maybe the DNS? The IP's are the same.
I'm trying to figure out how to link my Apache2 server running on AWS Lightsail to an application I'm housing that uses http://localhost:3000 when activated—it's a simple Node.js based CMS called Vapid. I have the server linked to my domain name—bigsheepcollective.com—and I can get Vapid running through the AWS terminal, but it's only the Apache2 landing page that shows up on my domain name. I saw a tutorial here that goes over establishing a proxy pass on an Nginx ran server but I'm not sure how to do the same thing for one using Apache2.
I've tried using the Nginx tutorial and I've also don't some extensive searches into proxy setups for Apache2, but I'm confused about what type of proxy I need when it comes to running an application that uses http//:localhost:3000.
Hi Bitnami Engineer here.
You can include these lines in the /opt/bitnami/apache2/conf/bitnami/bitnami.conf file or in the specific .conf file you created for your application
ProxyPass / http://127.0.0.1:3000/
ProxyPassReverse / http://127.0.0.1:3000/
This way you will access your application when accessing the public IP of your instance or its associated domain.
This guide in our documentation explains the whole process to configure a Node.js application on top of Bitnami.
https://docs.bitnami.com/aws/infrastructure/mean/administration/create-custom-application-nodejs/
I have the following setup in my DEV environment which is running on Windows 10 (which should be irrelevant).
Homestead with Virtual box to develop my Laravel applications
on my local OS I have a IBM Domino server running as dev1.mydomain.local
I'm trying to access the REST API on the Domino server from my Laravel installations. At the moment I'm getting 404 errors when trying because the domino server is not available from within the VirtualBox of Homestead.
Here is the network configuration of the homestead virtual box
Both webservers Domino and nginx on the virtual box are running on standard ports
Here is the ifconfig output of the virtual box
How can I make that possible?
UPDATE:
It just came to me that I am able to access the Domino server with LDAP, so perhaps changing the http and https port of the Domino server is already the answer...
I will test that and then get back here...
Changing the Port of the Domino server to 8080 enable me to access the server's REST API
dev1.mydomain.local:8080/api/data/
The connection to the local machine seems to be enable through the VirtualBox's second network adapter and the my call to the REST API got confused with the 2 web servers listening to the same port on localhost(127.0.0.1)
Update
although I was kind of able to connect to the server using the address above, still left me with the problem that authentication wasn't possible. In order to do so (and I have not the slightest idea why), I had to change to the local IP address of my PC to access the REST services
http://192.168.0.155:8080/api/data
If someone could explain that I would be happy :-)
I'd like to have a simple API running on a webserver (Windows Server 2008).
I've chosen Sinatra with its default Webrick backend.
What I'm not sure how to do is make my sinatra app visible to the outside world? I have remote desktop access to my server, I have the Sinatra app running, but I'm sure it's not configured correctly for response to outside requests.
I'd love any pointers in getting this going.
Figured this out.
Was pretty much as simple as ensuring sinatra was running with no ip (either run with -e production or use the -o 0.0.0.0 flag), and then most importantly, ensure the port the webrick server was running on was open on the windows server machine. Once the port was open, accessing it via ip:port works.