I have a https-website which I wanted to try out with another hosting provider, which does not support ssl for its test accounts.
I have copied all my data and databases from my old web hosting server to the new hoster.
I have replaced all https references in my database and in wordpress.
I checked the html source code and no https call is done there.
Problem: My javascript does not work on the page, the dev console says it renders a 404 error because it "Failed to load resource: the server responded with a status of 404 (Not Found) - https://example.de/wp-content/themes/mytheme/js/script.js". Why does it make a https call there ?
1) How did you migrate your website? Sometimes there are options with serialized arrays you can not just search/replace for HTTPS as this may not replace anything. For migrating your WordPress website use the following tool to convert the database (its de-facto standard):
https://interconnectit.com/products/search-and-replace-for-wordpress-databases/
This will most likely solve your problem and many others, too.
2) Furthermore do a search and replace on the code of your Theme (you said you have already done it)
3) External URLs may be called with HTTPS so make sure its not an external call
4) Check the server configuration of your new hosting provider - maybe the HTTPS is not the problem but there is something different in server configuration
Related
I have an IIS running on the server and a website (.net) running perfectly on http (80) and https (443). And i have a new Wordpress website. I wanna publish the wordpress site on the same domain. In order to do it i will remove the files of the present website and place the new site's files and in theory,i expect IIS will start to show this new site. And all the bindings and everything s set on IIS for this SSL certificate for the same domain. So my question is , can i expect that new site will run perfectly on http (80) and https (443)? Or will https fail?
Yes, in theory it should work but as you know with IIS, what is true in theory may not always be true in practice.
What you will find tricky is that Wordpress is heavily reliant on URLs and it may be tricky to run both options, ideally you should force one or the other but there are techniques that allow you to run both.
I can't speak for the effectivity or efficiency of this but here's a link: https://blog.rabin.io/sysadmin/make-wordpress-site-work-both-http-https
Well in theory it supposed to work but it didn t. Eventually i figured that SSL certificate was revoked.
I've developed a new WEB API 2 that works great locally, however when I upload the same code to my production server (Arvixe in this case) all I get is a 404 when I call it. I've spent HOURS searching the web, reading forums, etc.. and have been able to find no resolution, so I'm asking here as my last effort.
I'm currently only testing with the default project that gets created when you do New Project > ASP.NET Web API 2 Empty Project in Visual Studio. This creates an empty project with a single ValuesController. You should be able the JSON response by called /api/values, but this doesn't even work.
I'm using Fiddler to test the API locally and on the web server.
http://localhost:1993/api/values <--- works great
but
http://api.mydomain.com/api/values <--- returns 404
Note: I created a subdomain "api" in this case, but everything for the code for the API is unchanged from when it was created.
Why in the world does this work locally but not on the production web server?
That the server returns 404 (Not Found) may indicate a lot of things. However you can check using the following step:
Add a simple text document like readme.txt to your a folder sub-domain http://api.mydomain.com, and try to get access to that. If you can't access to that file, it means that the subdomain is not configured properly.
Publish the webservice using the "Publish" functionality, so that all DLLs will be copied.
After that,try to reach the Web ApI again.
Hope that help.
"Note: I created a subdomain 'api' in this case, but everything for the code for the API is unchanged from when it was created."
Above comment of your's is suspicious, you should publish your WEB API application in the root directory. Like if http://example.com is pointing to "MyExample" folder, then application should be published on "MyExample" folder.
After that you will be able access your api with http://example.com/api/{controller}/{action}
Just a simple suggestion which I'm sure you have already considered, but have you opened the http port 80 on the server's firewall?
Also stick a plain old html file in the root of your project and see if the server serves it up.
in your case, since you create a subdomain of 'api', you should try
http://api.mydomain.com/api/api/values
note that if you're using database for the function, you should change the connectionString in your web config
Please verify the .net framework on you hosted domain that may be old one.
Web api 2 is supposed on 4.5 framework.
One reason for web api 2 method working OK on local machine but not on production server is that the method you are calling is working on local machine but not on remote server. In such a case you will receive message 404 or 500, and you would be lost why this routing is failing.
Why a method would fail on remote server, well there may be many reasons. For me, I was querying database in my method and my connectionString was not set for remote server.
One way of resolving it would be to put some very simple code in that particular method and test that routing is working. Then check your original code for errors reasons.
I am using Mono + Apache for ASP.Net and when I go to the https version of my site it asks if I want to accept the certificate (I check to save it permanently) but then it shows a 404 error page! None of my pages show up under https. How do I fix this?
(What info do you need me to post to help diagnose this?)
I discovered the problem: Apache had a default "example" virtual host file to handle SSL requests. Even though I'd created my own, that one was taking precedence, so the directory of that virtualhost was being served for SSL.
I have set a plone product server with nginx + varnish + haproxy + 4 instance.(the buildout deploy configuration is come from the professional plone4 development book writted by Martin).
Now I have troubles with login process. I had to submit login info two times for signing in plone site.
I don't kown if nginx needs some settings like apache with mod_auth_ktk,or plone.session must adjust some parameters.
In fact , If I directly access instance using http://demo.com:8001/Plone address , it is OK.
Thanks.
There are potentially several causes of this problem, but the most common is a misconfiguration of the virtual hosting setup that causes some page resources to be served from a different URL than others.
View source on the browser, and look for differences in the URL between the page itself and the CSS/JS resources. If you find any, work on your virtual-hosting specifications.
I am building an asp.net web application which has been working on local and staging. however, when i deployed to live, there is a little weird issue occurred. below is the live environment details.
live environment:
Server 2003
IIS 6
when the request url is below, if page not found, it will redirect to page 404 configured in the IIS.
"http://www.xxxx.com/folder1/default.aspx"
however, when the request url is below (with a dot in the folder), it will show a IIS default 404 message which is "The system cannot find the file specified." which isn't what i configured in the IIS and it seems like it skips all the http handlers and modules. Therefore, my custom http handler stop working with this kind of url.
"http://www.xxxx.com/folder.1/default.aspx"
My guess it something to do with the IIS setting. i have have several research, there is no other issue like me.
appreciated if anyone can help. Thanks a lot.
Dion
One of the possible reason could be tool such as UrlScan - you need to explicitly configured it to allow dot(.)s in the url - this can be done by editing <Windows Folder>\system32\inetsrv\urlscan.ini and setting AllowDotInPath=1