I am hosting my website on firebase and for custom domain I am using freenom to get a free domain name. My domain name is divastra.ml
And I have successfully connected it with firebase and it is working too. But it is not opening with www.divastra.ml
It is only opening with divastra.ml
In firebase I tried to redirect www.divastra.ml to divastra.ml. Everything went ok but it is now showing needs setup in status.
I have done 2 process at the same time. First: connected divastra.ml with firebase. Second: redirected www.divastra.ml to divastra.ml
In both processes previously in status it was written needs setup. After waiting for few hours divastra.ml started working but in the second process(redirecting www.divastra.ml to divastra.ml) it is still showing needs setup.
Please help!
Thanks in advance.
Related
This is for a woocommerce site. I pulled the DB and the files locally onto my machine. I do have an SSL but I dont think that is the issue. When I run it locally I get the index page, which is under construction. The minute I try to login to the back admin part of wocommerce it immediately goes to the live URL online. How do I prevent this. I tried renaming the .htaccess thinking it was a redirect but it made no difference. If I shut the internet connection down, it still tries to reach out to the URL but says no internet connection available. Thanks.
in past week I had to change my server to cloud (Digital Ocean Droplet), I am using a shared service but the concurrent user reached the number of Php execution (30). I shifted the entire site and site is up and running successfully, moreover Yandex and Bing are able to crawl my website but it is Google that I want.
I have got like 100K errors in console dashboard and raising, google ads bot isn't able to crawl my pages too. I have checked the following and there is no error in these.
.htaccess and redirections.
SSL
DNS records (I shifted name servers to DO and then back to registrar to see if the DNS was the error) but it doesn't seem like it is.
I double checked robots.txt it is fine by the google robots.txt validator and other search engines.
Similar setups are running on other servers with no changes at all the are fine.
UfW, I am new to it but due to its temporary nature I don't think it is the reason. I disabled it and checked it doesn't make difference.
I haven't blocked anything on apache so it should be good too.
The error that appears is attached at screenshots
Help me out as instead of scaling, I am going down bad.
I repointed the DNS through another service it took its time but it is resolved. I wasn't sure about the error, now I am, it is because of improper or partial DNS resolution issue.
I'm attempting to run the project located at https://github.com/docusign/eg-03-csharp-auth-code-grant-core. I've followed all of the prerequisite steps listed in their read me file, have a newly generated Integration Key and Secret Key, and when I build the project in visual studio it runs without errors.
The problem is, whenever I try to sample links it redirects me to a docusign authorization page and when I put in my credentials it just gives me the message "The redirect URI is not registered properly with DocuSign".
I've gone to the admin portion of my developer sandbox and added the URL my project is running on http://localhost:8080. I also added in a second URL for where the example code should bring me http://localhost:8080/dsReturn, but I keep getting the same issue and I'm having trouble finding help online.
Could anyone help me with this? What else do I need to change?
The project runs on the following URL/port:this is the port the base project runs on
If your application is running on http://localhost:8080, the Redirect URI you register in DocuSign should be http://localhost:8080/ds/callback.
Note that the redirect URI is a specific landing page within the project, not the base domain.
Make sure that the URLs are registered for the correct integration key (clientId) you may have a mismatch between the IK you use in your code and the one you used to configure the redirect URI.
It take 2-5 minutes for updates you make to be reflected, make sure to wait a few minutes and try again.
URL must match exactly, http or https doesn't match
Confirm your port #. 8080 is not usually what IIS express is using.
I bought a domain name, www.toolshedfingerboards.com , and I already have a functioning heroku site here:
http://toolshedfingerboards.herokuapp.com/
I simply want to connect my domain to he heroku, and so I put the CNAME correclt, but when I go to www.toolshedfingerboards.com the URL automatically gets changed (as if an automatic redirect happens) from that of the domain (http://www.toolshedfingerboards.com) to that of heroku's (http://toolshedfingerboards.herokuapp.com/) . What else do I have to change, so that URL does not get changed? Thanks for any help guys!
I'm migrating over a test site to AWS from another company. They've been nothing but unhelpful in giving up the necessary credentials and info to make this a seamless transition.
My test site, now, has everything it needs to be a perfect test site. Looks exactly like the current up and running site, has all the databases, necessary bells and whistles. The only issue is that my AWS public DNS is redirecting to the live server.
I've tried removing all .htaccess files from the EC2 instance and the S3 buckets. I've tried searching for any and all files that would cause this redirect. The live server has nothing on it that would cause this as well.
The IT department of the client only knew that there was some code injection in some file to help redirect every URL the client owns to the same site. I'm at my wits end with non-cooperative dev shops and don't want to spend more time digging through endless files for some few lines of code.
Am I forgetting / missing / overlooking something here? Before I go crazy.
What do you mean unhelpful giving credentials and information? AWS is a IaaS company, you are responsable for the setup and configuration of your servers. They do offer a paid support plan if you will like to purchase it but it's pretty straightforward to get your access keys when you create an EC2 or RDS instance.
Why don't you fix you problem at the dns level? Simply create a subdomain where you will host the temporary test site on the testing server, see if everything works and then change the dns configuration to the live server.