I have the weirdest problem. I deployed my app to heroku and registered a domain name lets say: xyz.example . I tried to move to this URL and my project was there and working fine, then I tried to move to www.xyz.example and I get a completely different project that exist in my computer but have nothing to do with heroku and never have been deployed to there! Its a static website that has been uploaded to another domain using filezila a while ago. My domain provider is Domain.com. I tried to look there for answer in my domains list but nothing has changed and it's all looks fine. What can it be?
To connect your heroku hosting to your domain name,
you have to open your domain name account and in the DNS Management page add in the cname the host: www and in the point to: your heroku url And in the heroku page in the settings add three domains:
*.xyz.example
xyz.example
www.xyz.example
This should work :) Check this video https://www.youtube.com/watch?v=kKGSGT7mSnQ&feature=youtu.be
Related
I own a domain through GoDaddy with the .app extension (call it mydomain.app). I have a site hosted on Firebase Hosting for this domain and it works fine. However, the website only loads through https://mydomain.app and not https://www.mydomain.app. I have the DNS properly configured according to GoDaddy tech support and wonder if I'm supposed to explicitly add www.mydomain.app in Firebase hosting in addition to mydomain.app? Seems redundant. Or is this not necessary and I have a configuration problem on my hands?
Go to GoDaddy, where you added your A record to point to Firebase the first time.
Since it's working, that means you configured it to use
# ==> your FirebaseAppUrl.
Under it, now, add also another A record, to configure your www.mydomain.com,
by adding www A record, to point to the same place.
www ==> your FirebaseAppUrl.
Keep both records of course in GoDaddy.
I inherited a site that worked on the domain.
Hosted on a plesk server from GoDaddy.
I placed a new site on oldguard.org which is hosted on ionos (formerly 1and1) and is working fine as is...you can see it at https://oldguard.org.
I wanted to take the old site that use to be on oldguard.org (current plesk site) which I can't not get to load at all, and place it on a new domain http://demotoga.com.
I have checked the servers with the domains and everything seems to be pointing in the right directions. However, when you go to demotoga.com, you get redirected to oldguard.org which is hosting the new site. For some reason, the old site (plesk location files on Godaddy servers) will not load on demotoga.com no matter what I do. It just keeps redirecting to Oldguard.org.
I believe the problem lies in the web config file for the hosting files that are for the old site which use to live on oldguard.org but cannot locate why the site continues to redirect. Shouldn't the site appear on demotoga.com if everything matches up?
I've looked around and around and cannot find where it points to the oldguard.org URL. What other Information is needed to solve this issue? Happy to provide any coding or give additional information just not sure what is needed to solve this issue.
Full web config code can be found here:
https://www.oldguard.org/wp-content/uploads/2018/12/oldguard-oldwebconfig.pdf
I have a working blahblah.firebaseapp.com default domain working correctly. No problems there. My website was on another provider so I went through the process to connect it to firebase hosting. Everything went fine and the domain status in Firebase Hosting console shows connected for my blahblah.com and www.blahblah.com domains. My problem is that when I navigate to blahblah.com, I get a page that says
I can't find anyone with quite the same issue on Stackoverflow or any other site. There was one that was fixed by opening in a different browser (cached site issue), but this isn't my problem. I have double checked the DNS settings from my provider. Everything checks out. It's been close to 20 hours since I have completed the verification and the status shows connected in firebase hosting. I even re-deployed my site to firebase to see if that would reset something. Didn't help.
So now what should I do? Any ideas?
Assuming you initialized your project with default values, your public directory is what get's served. So, edit or add the index.html file in your public folder then firebase deploy. You should now be able to see your custom HTML.
I had also the same issue, experimented a bit and found the solution.
Case 1- You want your website to be served at subdomain.domain.tld as will as on domain.tld, but added only subdomain.domain.tld as custom domain on firebase hosting dashboard.
In this case the address domain.tld will throw an error.
To get rid of this error add another custom domain in your firebase
hosting dashboard as domain.tld
Case- 2- You want your website to be served over domain.tld but also accessible through subdomain.domain.tld
Add both the domains in custom domain field.
Edit subdomain.domain.tld to redirect at domain.tld.
Case- 3- You want your website to be served over subdomain.domain.tld but also accessible through domain.tld
Add both the domains in custom domain field.
Edit domain.tld to redirect at subdomain.domain.tld.
I have about five different subdomains on my host that are all working fine with wordpress installed.
I recently switched from Godaddy to Namecheap and bought a new domain name.
I changed the domain on my WHM Server which was all fine with my current sites.
The problem I have is when adding a new subdomain and installing Wordpress the site breaks because of DNS issues.
The Wordpress auto install is also weird as it doesn't detect the root like it used to, it puts the sub domain name into a folder above public_html.
So old subdomains are working fine but adding a new subdomain brings dns errors with wordpress installed.
Any ideas please, I've spent a solid five hours on this already.
Thanks.
If I'm following you correctly, you...
Created an account and bought a new domain on Namecheap
In Namecheap's WHM (Webhost Manager), you changed the domain to the one you had with GoDaddy.
When you create a new subdomain in Namecheap's WHM, it's not resolving the subdomain
So based on the above assumptions, it sounds like your domain is still with GoDaddy, and it's still pointing to GoDaddy's name servers. So if you add a new subdomain in Namecheap, it won't do anything, because Namecheap doesn't have control of the DNS. And for that matter, I think your subdomains would still be pointing to GoDaddy's servers.
Again, assuming I followed your description correctly, I'd recommend you migrate your old domain to Namecheap since, I'd assume, you're going to close your GoDaddy account at some point. If you need to urgently create a subdomain, you would need to do that on GoDaddy's end.
Hope this helps.
Fixed the problem myself, for anyone with a similar issue. I even went through Hostgator support who couldn't figure out the problem.
Logged into WHM > DNS Functions > Edit DNS Zone
The sub domain in question was not named correctly, it was named as the directory name instead of the full url.
I have a wordpress site hosted on WAMP on my local PC. I want other people on my network to view this website but when I tested it from another PC none of the stylesheets, scripts etc are being loaded. I troubleshooted it and found this is because it's looking for those files on localhost. How can I change it to look for those files relative to the folder? Thanks
What you have done is a bit like moving the site to another domain. Because WP records the domain name in its database when you install it, it thinks its domain is localhost.
Now you are getting to it by lets say using your ip address 192.168.0.10 this is considered a new domain name and when it attempts to server various resources it is still using the original domain name of localhost it cannot find those resources on the other PC's.
You can find out what you need to do here on the worpress site Changing the site url
I solved this by using my IP address as the site path in Wordpress/Settings/General