I have been trying to deploy a product version of my django application. For that, I have been informed that I must follow the following tutorial: https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-14-04
to setup and run my application on nginx server using gunicorn. I followed all the steps and everything went fine. But in the end of this tutorial it says that:
If no errors are reported, go ahead and restart Nginx by typing:
sudo service nginx restart
You should now be able to go to your
server's domain or IP address to view your application.
but when I go to my ip address, I see the default nginx page. Screen shot here:
screenshot
Can anyone advise, what can I do to see my actual website from here by visiting my ip address in browser?
Try restarting gunicorn service also. I would suggest using automated deployment methodology rather than manually doing it, like dokku, mina etc.
Related
I have a docker image running instance of Apache Superset and some other services on the same VM. The other services are setup and deployed independently from the Superset app. What I would like to do is to be able to redirect via url from the Superset app into the other apps. Obviously simply passing url will redirect me inside the container.
The optimal solution would not require me to include the other services into docker container and also allow for some cross service authentication.
I'm not sure how to approach this.
Please help.
I trying to mount a docker-compose stack with a mariadb and proxysql and all works fine. When i navigate to https://172.25.0.174:6080/ (the VM that holds docker stack), the browser shows the ProxySQL Web UI. On top of this stack, i mount another VM with HAProxy not using docker at all. This last VM routes requests across several other services. All works fine, but ProxySQl Web UI. When i navigate to admin.testdomain.com/proxysql (HAProxy route this address to 172.25.0.174:6080), the browser ask me for the authentication, but then a 404 Not Found error is thrown.
It seems that the problem is the digest auth that ProxySQL Web UI uses. I tried many config options on the HAProxy side, but no one seems to work.
Anybody can help me, please?
I deployed an application (let's say app1) in GKE with a service, deployment and certificate setup in an existing cluster with Jenkins and another app (let's say app2).
The other app is deployed in the same way as the new one, with a certificate (and a static IP and DNS entry).
Jenkins is not exposed to an external IP, so I used to use the port forward option in the cloud console and then web preview - this creates an appspot URL which alloww me to login to the web admin.
Something strange happened after I deployed app2.
I tested it with the webpreview button and could reach it.
All was fine and it was accessible at the new URL with HTTPS and all.
But after that, the web preview to Jenkins was not working anymore.
Instead, I would be redirected to app2, always.
I could not figure out why, so I removed everything from app2 and now I have some very strange situation:
in the (Chrome) browser where I did most of the actions, I can still access the (broken) app on both the FQDN in DNS and on the appspot link ( https://8080-dot-1234567-dot-devshell.appspot.com/ even after I reboot, clear cache and logout the google account (and removed the statis IP even) - the port forward actions works and gives the above link (with other numbers)
in another (Chromium) browser on the same laptop running Ubuntu, the portford action works, but when clicking the link in the browser it does not generate another appsot url and fails with a 500 error screen
After reading up a bit, I understand there is some proxy that is used to do the forward, I expect the proxy to be 'hanging' some how and on top of that it seems there are application left overs in the cluster that should really not be there
I have basic support currently, so not eligable for technical support.
I cannot find a manual way to access the appspot proxy and I found no load balancer or any other thing I know of that may cause this.
If I run the portfoward in the cloud shell in the second browser, I can curl to the localhost on the exposed port and get Jenkins, so that part seems to work, but the web preview then does not.
How can I go about troubleshooting this (meaning getting back to the web preview working for Jenkins and getting rid of the application left overs)?
I actually found the cause of this issue with the help of a colleague.
The second application I deployed was Yopass.
It turned out that it uses a serviceworker, that cached (almost) everything in the browser, including most of the application, I suppose to run offline.
Although I tried clearing cache in the network tab in developer options, I still had this behaviour which made me think it was not a cache issue.
After removing all cache in the applications tab for both the FQDN url and the appspot domain, behavior went back to normal.
I was not able to fix it in the other browser yet, but I suppose that is cache too. Thanks for the help, I consider this solved.
I am trying to host a WCF RESTful service in IIS as a child application under and existing Site but it will not work. It works fine when I host it as a Site by itself, but the problem is that both Sites share the same port numbers, port 80 (http) and port 443(https). Can anything help with how to get around this?
You must select the default site, do right click and add application or create a virtual folder to point to default folder where your service is in dev...
If you choose the first you need to create a file system of the service, with publish in Visual Studio.
and
.
So with this approach you can use the same port with different route.
Thank you for for taking your time to answer the question. I was able to get the solution myself. It was because I did not configure HTTPS when I hosted the service in IIS. After I configured the HTTPS, everything works great.
I want to deploy my Meteor project to my own domain. In the docs it says:
"You can also deploy to your own domain. Just set up the hostname you want to use as a CNAME to origin.meteor.com, then deploy to that name.
$ meteor deploy www.myapp.com
We provide this as a free service so you can try Meteor. It is also helpful for quickly putting up internal betas, demos, and so on."
Is this what I need to do? What does this even mean? I don't know what a CNAME is or how to set up my hostname.
Over a year late but perhaps relevant for anyone else with this question, since the comments and answer given seem to miss the point - which is not about deploying to your own server but rather configuring meteor.com hosting to use a custom domain.
Meteor.com offer a free service that is intended for demos and internal betas - the very early days in the life of a site.
You can use meteor deloy without configuration if you are deploying to a subdomain on meteor.com -
meteor deploy myGreatHope.meteor.com
However you can also host your app on meteor.com using your own domain but to do that you need to be able to set up an alias which is done through CNAME A records
These are setup on a server that would otherwise host your site - So you will need a host - it could be really cheap one, and it could provide email hosting for you, ask them to create the A records (or look up your control panel help files) so that they resolve to origin.meteor.com and then you have your site, deployed to meteor.com accessible through your domain name.
If you want to deploy Meteor on your own domain, I wrote a tutorial on the subject. If you are running Nginx, it should help you. Otherwise, if you are running Apache, check the second one.
Deploy a Meteor Application on Ubuntu with Nginx.
Deploy a Meteor Application on Ubuntu with Apache.
And of course, you need to understand and configure your DNS. This two tutorials helped me a few months ago.
An Introduction to DNS Terminology, Components, and Concepts
How To Set Up a Host Name with DigitalOcean