I am facing an issue with sitecore coveo installation on my dignostic page
The remote server returned an error: (503) Server Unavailable. (Hide details)
System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
at System.Net.HttpWebRequest.GetResponse()
at Coveo.SearchProvider.Applications.StateVerifier.<>c__DisplayClassd.<GetRestEndpointState>b__c()
at Coveo.SearchProvider.Applications.BaseVerifier.VerifyComponent(Func`1 p_VerifyMethod, String p_ComponentName)
although i have found some solutions related to this on forums but not one reflect the same.
https://answers.coveo.com/questions/1974/rest-endpoint-the-remote-server-returned-an-error-503-server-unavailable
same goes for below error not reflecting or fixed by using provided solution.
https://developers.coveo.com/pages/releaseview.action?pageId=14058186
Thanks
Since you get a "Server Unavailable" exception for the "Coveo Search REST Endpoint" component, you should ensure that:
The "Coveo Search API" software is installed either on the Coveo Enterprise Search server or the Sitecore server depending on your infrastructure.
The "Coveo Search API" Windows service is started on the machine it was installed on.
The "Coveo Search API" logs doesn't contain recent errors that may prevent it to run correctly.
The "Coveo Search API" listening port (default is 8080) is not used by any other software on the machine the "Coveo Search API" was installed on.
The "Coveo Search API" listening port is not blocked by any firewall.
The server on which Sitecore is installed do not block requests to the "Coveo Search API" listening port.
You can access the "Coveo Search API" URL (default is http://ServerName:8080/rest/search) from a browser on the server on which it is installed.
You can access the "Coveo Search API" URL from a browser on the server on which Sitecore is installed.
You can access the "Coveo Search API" URL from a browser on another computer.
You can access the Coveo for Sitecore REST Endpoint proxy URL (default is http://SitecoreInstanceHost/coveo/rest) from a browser on the server on which Sitecore is installed. (/coveo/rest must be in lowercase)
You can access the Coveo for Sitecore REST Endpoint proxy URL from a browser on another computer.
Let me know if it helps.
Jeff
Related
I've previously had Web Deploy up and running without any issues. Following a company wide installation of Bitdefender, Web Deploy has stopped working. I've tried the following without any success
Added the following rule to Bitdefender firewall
Local Address: Any
Remote Address: our server IP port 8172
Protocol: TCP
Direction: Both
IP: Any
Network: Home / Office
Permission: Allow
Using the following telnet command, telnet [IP address] 8172, I get a blank screen.
Navigating to the URL for the publishing server connection, I'm prompted with a login and then a blank screen.
I don't have Fiddler, or anything similar, running.
I've tried on other machines in our office yet I get the same response.
Re-installed Web Deploy via Web Platform Installer Recommended Server Configuration for Web Hosting Providers and using command prompt I've restarted the agent services with the following commands
net stop msdepsvc & net start msdepsvc
net stop wmsvc & net start wmsvc
I've added IIS Manager Permissions to the appropriate site in IIS, using the server administrator account (which worked in the past) and configured web deploy publishing.
I'm running out of ideas of what to try so I'd appreciate any suggestions.
When attempting to validate the connection in Visual Studio I see the failed notification, "The operation has timed out".
The problem is in the Policies for Content Control. Exceptions need to be added for the sites you would like to web deploy to.
Click on policies, then go to the policy that applies to your development system. In my case this was "IT Policy." If you don't know, you can go to Network and drill down through Active Directory to find what policy applies.
Next, go to Content Control => Traffic. Check the boxes for Web (HTTP traffic) and Traffic Scan exclusions. Then add the URL or IP address for whatever system you are trying to deploy to (We used IP).
Hope that helps!
I can access upsource locally using http://pcname:42424/projectname/view.
Trying to access it using the IP eg. http://192.168.1.42:42424/projectname/view yields
OAuth 2.0 Error
unauthorized_client: Unregistered Redirect URI. Client service
'Upsource' requests authorization entity for the URI which is not
registered in Hub: http://192.168.3.143:42424/. If you have Hub
administrator permissions and the suspicious URI does belong to
'Upsource', please add this URI to the list of 'Redirect URIs' in the
service settings in Hub
With link to https://www.jetbrains.com/help/hub/2.0/OAuth-2.0-Errors.html#auth.unauthorized_client
I could not find how to set redirectUri though in Upsource (went through maybe all of the settings pages).
Where can I find the redirectUri setting so I can add my IP to it?
Update
I set up another instance on a different box and set the URL and port to be http://192.168.1.42:42424 and now it works successfully to be accessed remotely using the IP.
For some reason the redirect URI settings area is hidden in Hub even if you're an administrator. I was searching for something else in the JetBrains knowledge base and came across this page which led me to try to add /services to the end of my hub url in my browser:
http://my.serverurl.up/hub/services
Which brings me to this wonderous page with a bunch of configuration options that I can't access through the Administration UI:
FWIW: What I was trying to do initially was configure UpSource to be accessed through a reverse proxy on port 80, instead of the default 8080. I moved my UpSource configuration from one server to another and read the documentation from JetBrains on the subject but it wasn't working.
My mistake: I didn't stop UpSource before running
<upsource_home>\bin\upsource.sh configure --listen-port 1111 --base-url http://upsource.mydomain.com:2222
and UpSource didn't warn me that the command wasn't doing anything. Its message was "UpSource is now running". I stopped UpSource, applied the change and restarted and everything worked. I should've known but I didn't.
Hope that helps someone.
I am trying to install and configure SiteMailBox on SharePoint and when i execute the .\Set-SiteMailboxConfig.ps1 i get the error :
Get-SPAppPrincipal : The HTTP service located at
http://app:32843/87f2cfd3c96f4130b4f269d7cae8d99b/AppMng.svc is unavailable.
This could be because the service is too busy or because no endpoint was found
listening at the specified address. Please ensure that the address is correct
and try accessing the service again later.
I went to IIS Manager and i wanted to verify my SharePoint Web services status, so i wanted to browse to the http://localhost:32843/Topology/topology.svc and i got the http 503 error service unavailable... According to this thread
Can anyone suggest me how can i solve this probelm please ?or even some suggestions?
My appManagement is set up and here is my IIS site with its bindings :
Changed your Admin Password??
Need to fix all login references
See Application Pool -> Advanced Settings
-> Identity
I can't seem to be able to deploy a site to a windows server 2012 r2 running IIS and Web Deploy in Azure VM. I have verified that the port is open, the credentials are correct and the site name as well. I tried using http: and https: also tried using msdeploy.axd end point and the MSDEPLOYAGENTSERVICE one nothing. Check is the services are running and if I can connect to the machine which at can on port 80 to the default site. Tried connecting from multiple connections I get the same result...
Could not connect to the remote computer ("<computer name>.cloudapp.net"). On the remote computer make sure that Web Deploy is installed and that the required process ("Web Deployment Agent Service") is started. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE. Unable to connect to the remote server.
After dealing with this for about an hour now, I figured out how to fix this on my Azure Virtual Machine.
First the obvious
Check that port 8172 (if you're using default settings) is open in your firewall
Check that the processes MsDepSvc and WMSVC are running.
Check that the site name is correct.
Management Service
In ISS, at the root level of the server, check your settings under Management Service.
It should have Enable Remote Connections checked:
Did you download the full package
This was the one that got me, I hadn't installed everything.
On the bottom of the WebDeploy page: http://www.iis.net/downloads/microsoft/web-deploy
You can download the full package, and then just install everything.
You don't mention if you have an endpoint configured for your Azure VM. If not, make sure you create an endpoint with a private port of 8172.
EDIT: Here is a troubleshooting guide for web deploy that includes the error message you've encountered. Additionally, from my own experience I have managed to mistype the site name and not install .NET and seeing similar errors.
Helpful but in the end in our case it was TLS mismatch. Check both machines can do TLS 1.2 if you are forcing it. Have put more detail here https://fuseit.zendesk.com/hc/en-us/articles/360000328595. Cheers
I recently deployed an ASP.NET MVC4 website to Azure website. However anytime I am on a proxy network, I wouldn't be able to connect to the services.
How to connect Visual Studio Azure SDK1.3 to the Azure Website Over proxy server. Below is error message:
There was no endpoint listening at https://management.core.windows.net/3e541adf-2b85-4ff1-b066-a40f11f6e4a6/services/?servicelist=WebSite&expandlist=Service that could accept the message.
This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
The remote name could not be resolved: 'management.core.windows.net'
The very last line of the error says it all:
The remote name could not be resolved: 'management.core.windows.net'
The proxy you are using blocks or has DNS resolution issues for the management.core.windows.net domain. There isn't much you can do about it, besides using another proxy or not using proxy at all.
If you're able to whitelist domains on your proxy, or know someone that can, you will want to whitelist management.core.windows.net.
This may help, it explains how to use a Port Bridge to get around your problem.
http://www.dotnetsolutions.co.uk/blog/connecting-to-sql-azure-without-changing-your-firewall