We have configured the SSL on SharePoint 2016 environment, however the search crawl is not working on SSL URL site. It works for internal HTTP URL though. I tried the below article but no luck:
https://blogs.msdn.microsoft.com/sharepoint_strategery/2013/02/20/beware-crawling-the-non-default-zone-for-a-sharepoint-2013-web-application/
https://blogit.create.pt/miguelisidoro/2018/08/10/sharepoint-2016-problems-crawling-content-and-the-the-crawler-could-not-communicate-with-the-server-error/
Please let me know if anyone else has faced same issue and resolved it.
Related
In my company we use the Web Portal to log users into the RDS2016 Terminal. Firefox has been giving me the error for some time: "Parts of this page are not secure (such as images)". I know this is related to hardcoded http instead of https and pointing to favicon.ico. I also know that in Wordpress it can be easily solved with e.g. Really Simple SSL. On a server we use common IIS in windows server 2016. I can't find a favicon link to fix it from http to https. The favicon.ico file is in / root.
We have a cpanel server that hosts some web sites. we have 2 hosts that use SSL. When I open a non SSL website with http:// everything is ok but when I type https:// , it shows the contents of one of the SSL websites instead of displaying not found error!!
Usually the first one which is defined in httpd.conf.
I also signed up in cPanel forum, but I do not know how to post a new question!! I cannot find post a question or new post or something like that.
Any help is appreciated.
Your question is really confusing. It would be better if you can edit and elaborate your question. Still let me guess your question and answer it.
Your cPanel server has hosted more than one websites, out of them only two have SSL certificate. Let me guess those two sites as abc.com and xyz.com. Now if I have understood your question properly, when you try to access 123.com (which is non HTTPS website) with HTTPS it is showing content of abc.com.
If yes, then this case refers to SSL misconfiguration. To solve this issue, SSL certificate should be installed properly on both websites and only those two sites can be accessible with HTTPS. It is advisable to use SSL Certificate checker for both sites to know whether SSL is installed properly or not.
So this afternoon users started reporting that they couldn't get to our SharePoint 2007 intranet site. We set the home page via group policy for all users to the url
http://spsite
When this url is hit, SharePoint redirects to
http://spsite/Pages/default.aspx
This has been working like this for years.
Today, our remote branches are getting returned a 'Under Construction' page. However, if these same users hit Refresh on the browser or type in the
http://spsite/pages/default.aspx
they get there without issue.
Our local users are not seeing this problem at all. This tells me there has to be some kind of DNS resolution problem. I'm not much of a SharePoint guy, so I'm at a loss.
Has anyone seen this behavior before? What would be my first step in trying to figure out where the problem is?
I'm posting the resolution for this and the theory behind the issue.
There were a few things that happened in our environment that lead to this 'Perfect Storm' scenario.
At some point in the day, our SharePoint site became unresponsive. Users hitting the site at that time then got back an odd response from the server. It seems that somehow IIS had two sites listening on port 80, both with a wildcard binding. The first site was the SharePoint site, the second one was the default site. When the SharePoint site failed to respond, IIS then went to the Default Site. Since this site hadn't been set up, the 'Site Under Construction' page was returned (IIS6 on Windows 2003 server).
This was odd in itself. However, what happened later is just as bizarre. An IISReset fixed the problem that the SharePoint site was having. As a result, the SharePoint site was again available. However, anyone that had hit the url when it was down had a cached the iisstart.htm page. It appears that when their browser was checking the URL, they were getting a 304 from the server. So the request never made it all the way into the sharepoint site, which actually returns a 302 redirect.
So, for all these users, we had to clear the cache on their machine and this then allowed the to get back to the SharePoint site.
I am using sharepoint search server express 2010, And have bit of a trouble in crawlling. The pages that are permenantly redirected are not crawled and come up as a warrning that the url is permenantly moved, where as this isnt the case with the pervious version of search server where it would just crawl
Is there any config setting that I can change on the search server 2010
Thanks
We upgraded a wss 2 site according to Microsoft standard (prescan, migration etc) and resolved smaller issues on the way.
However, now we don't receive any errors, and when we access the site in wss 3 it gives us a 404 - page not found error. We now there is a site at the root, and wss confirms that...anyone knows what's wrong?
By the way: We also upgraded another site the exact same way and it works beautifully...
What does the log file say?
Is the content database correctly setup? (Name / Server.) More specifically, the permissions for the pool account.