So Ive had this practice project deployed for a while, but the issue is now when I connected a domain name to the deployment, it suddenly doesn't work?
the website works perfectly when going to the ip address 18.222.146.180
but when putting the domain thats attached, http://stockstrack.org/ it suddenly breaks and has no css??
I even added other things ive found online into the application file to ensure that it read/attached the css, and still nothing? This whole thing was created with ruby on rails using postgres database. Any help is greatly appreciated, thanks.
You have a incorrect virtual host settings, Check again your webserver's virtual host entry.
Related
I'm using ahoy_email ruby gem to track the emails I send. It should give me the time at when it is opened and clicked. But it's not working properly to give the time. What I'm missing.
Note: I run the project in my localhost
I had a similar issue. Make sure your server is accessible from the outside world so the image can be fetched.
A little background: I eventually figured that it worked from the godaddy webclient but not gmail, and thats because the webclient was just loading the image from my browser (so it could see my 'localhost'), but I believe gmail uses a proxy server to load images (https://filippo.io/how-the-new-gmail-image-proxy-works-and-what-does-this-mean-for-you/) so it couldn't find it.
I've been using ngrok lately to make my localhost outside accessible (temporarily!) and been liking it.
I moved an app from my existing ISP to heroku 2 days ago.
It seems like it wasn't working until I realized I had put railslinks.com instead if www.railslinks.com in the heroku web control panel interface.
So when I actually tried http://railslinks.com instead of http://www.railslinks.com it worked
So (today 1 hr ago) I added www.railslinks.com in the heroku control panel.
I made NO changes to my DNS settings with Network Solutions (which show all my various domains with the www prefix).
So far though, I'm not yet able to connect to http://www.railslinks.com
Is there a dns-like delay in getting my heroku change propogated or am I missing something.
Note: 'myapp' is not the actual name, just my placeholder in the document.
DNS Settings at Network Solutions:
Heroku Settings (I've put both of them there for now, tried www alone didn't help):
Found it, have to use my "zergio" dns editing tool:
Provided you have a CNAME entry for www.myapp.com pointing at either proxy.heroku.com or myappname.herokuapp.coun then it should work.
Adding domains is almost instant on Heroku, this sounds more like a DNS issue but without knowing your real domain makes it tough to diagnose.
For me this has worked out for www.reactjs.co (just add www. in the heroku app admin panel):
herokuapp fix - click here for the screenshot
I've been working for a client's website over the past year. I usually test things locally and then deploy straight to the production website. This has caused us some issues lately so I thought I should create a test/staging environment in which we could thoroughly test new features before pushing them into production.
Anyway, we have a VPS hosting account. I usually use remote desktop to manage the website in IIS. So in order to create a test environment, I copy pasted the folder of the production website inside the same directory (so they are both at the same level) and changed the name of the folder. Then I created a new website in IIS and mapped the physical path to the httpdocs folder inside the copied folder. After that, I setup a new application pool which basically has the same settings of the production website's application pool. I also changed the connection string of the test website.
But then when I tried to view the test website, it did not work the way I expected it to do. I keep getting &ReturnUrl=%2f appended to the query string, and the website is stripped out of its styles (the CSS). I remember this used to happen before when we were still using a shared hosting account, but I have no idea how to fix that.
I really do not know what's wrong. I basically have the same exact setup except I'm using a different port and a different database. I even tried running the test website with the application pool of the production website, but that did not work either...
Any suggestions?
looks like permission problem to me, check if your user has correct privileges in the new folder/app pool :)
I've recently installed Pow on my Mac. It's great.
It's convenient for my own dev machine. But I wonder if I can set it up to be shared by my colleagues. The problem is DNS resolution part.
For example, if I have a dev site on my machine like "http://myapp.dev". How do I let my colleague access to the site on my machine from his machine?
The hacky way to do this is to make them edit their DNS and insert a record in /etc/hosts that maps to your machine. An easier way to do this is Localghost which doesn't require editing files by hand.
I've been using https://showoff.io and it works a treat. Also allows others not on local network to view it as well (if that's something you need).
I am facing a strange issue with azure -
After uploading a new version of my app about an hour back, the public facing url is throwing a runtime error. However the app works fine when I access it through the azure internal domain -- app.cloudapp.net.
Before upgrading it was working fine.
I have rechecked the cname records with my hosting provider (bluehost) but I cannot find any problem. Even otherwise, the problem seems like an ASP.net issue (due to the typical error page rendered) but something that just does not make sense.
Anyone has any ideas as to what I can do?
EDIT: This started working just as mysteriously as it had stopped - I have no clue whether it is due to DNS propagation delay (although in that case it should not have thrown an error page like described above). However if someone knows why this might happen, I will still appreciate it.
There is a DNS service available for Windows Azure called "DNS Azure" that changes your cloudapp's IP address automatically. See dnsazure.com
This solutions helps to avoid the CNAME record because the A record is kept up-to-date.