My TFS is working fine for: http://localhost:8081 (notification URL).
But my other domain: www.sub.mysite.com (example), which succesfully resolves to other sites inside my IIS, will simply not load up TFS. Basically it sits on "connecting" then eventually times out.
What I don't understand is, when I change the URL in the TFS Admin console, I've noticed it doesn't even update the IIS bindings.
What can I do?
This could be the the old double-hop issue? But I can't really tell as the question isn't specific.
Related
I've been installing our very own ArcGIS Enterprise instance on AWS.
The instance I chose is ArcGIS Enterprise on Ubuntu.
It is important to mention that this installation was conducted without using Cloudbuilder. I know it is a tool that automates the process but I was introduced to it only after I have already started to attack my current instance problems head-on. So, please don't advise me to restart the whole process from scratch using it.
The current status of my instance is that my ArcGIS Server is working. I can access it, upload services and we have already started using it in out Staging environment.
I have authorized all of the software on the server and verified it is licensed. The Portal for ArcGIS is my main problem.
Whenever I try to access it externally(from my office computer) it seems to redirect to the internal IP for some reason, and then times out on that request.
for example typing(from my browser):
https://[dns address]:7443/arcgis/home
redirects to:
https://[internal IP]:7443/arcgis/home
and this times out. (...took too long to respond error)
The funny thing is I can access the portaladmin area.
it's only the portal itself which doesn't work.
Also, another curious thing is that if I type without using the ports, I can access a window but exceptions are thrown in the browser.
For example:
https://[dns address]/arcgis
This will lead to a window where the ArcGIS world icon can be seen but nothing else loads and there are exceptions for "resource not found" 404 on some of the components of this page.
Any ideas? What further information should I include to answer this question?
I've looked everywhere but Esri's documentation is not very forthcoming with examples and information to understand what it is I did wrong.
Also, I don't think this is a ArcGIS software issue. It looks like this might be a proxy issue. Anyone else experienced something like this?
Thanks!
I found the solution.
It was a combination of two problems:
Tomcat that was running the web adaptor service was crashing because of an entirely different and unrelated issue.
The Portal was missing a web adaptor configuration and therefore did not have the WebContext property set with the web adaptor URL.
After fixing both of these problems, I was able to access the portal correctly.
I'm running windows 10. I used to use github just fine and I'm not sure what changed, but I can't access the site in any way. I can't browse it. I can't use github tools. I've tried http and https. It all times out.
All other https sites work fine. All other sites that I can find in general work fine. It's just me and Github not getting along.
I beseech thee, code gurus, help me get back to work.
I've tried setting myself in the DMZ of my router and turning off the firewall, to no effect.
are you about to connect to this ip?
192.30.252.153
192.30.252.154
You should get this page
Comment on whether you get this or not you get this so I can help you
It went away as mysteriously as it came. We may never know.
My website at Azure suddenly started showing a basic "Umbraco welcome site" instead of my website hosted on azure. I do not know why, Umbraco is not included in my sourcefiles as far as I know.
When I do http://www.mywebsitename.com it works fine and my azure website gets loaded, but when I dont include 'www'; http://mywebsitename.com - it just shows the "Windows Azure Accelerator for Umbraco" page saying:
"The Windows Azure Accelerator for Umbraco is designed to enable Umbraco applications to be easily run on Windows Azure. The accelerator has been designed to enable you to rapidly deploy Umbraco applications and updates to your application without redeploying a full Windows Azure Service Package. For more information about the accelerator, please visit the CodePlex site located here."
I do not know why this behaviour suddenly happened, how can I get rid of it? I think maybe this behaviour started when I played around with some storage-blobs
Is your DNS set correctly for the URL without the 'www.' and is your Azure app listening for both www. and the empty subdomain? Sounds to me like the URL without www. is hitting a different application.
I have a DNN site (5.06) that I developed on a standalone machine running IIS7. When I copied the site to the production machine running IIS6 and enter the URL, such as www.site.com, I get a generic DNN error page with no additional information. However, if I add the default page, www.site.com/Default.aspx everything works fine.
The Friendly URL settings were never changed and I've verified Default.aspx is entered on the Documents tab in IIS6. The portal event viewer has no entry for the error page I get.
I'm nearly certain it has to do with migrating from IIS7 to II6; clearly I'm missing something here. Any ideas?
DNN has confirmed this is an error in 5.06, and will be addressed in a future update. That doesn't help me today, but I was able to work around the problem by adding the following to the Friendly URLs list:
Look for: .*/
Send To: ~/Default.aspx
I can't find the forum thread I was reading yesterday, but did find this one which also goes into detail on the issue: Error upgrading from 5.5.1 to 5.6.0
Pretty odd...
Double check PortalAlias table in your SQL server. Confirm www.site.com is in there.
Double check host headers in IIS6 has www.site.com
Make sure Default.aspx is in the documents area of IIS6 and set as the top default to run
Recycle your app pool
cross your fingers
Only thing I ever run into from IIS6 and IIS7 is in the app pool running in Integrated mode or classic... but that is usually as issue going from IIS6 to 7, not vice versa.
I was able to fix the issue (for me) by taking the web.config file from a working site with the same version of DotNetNuke and modifying it to have the correct machine key and connection strings. This is my last resort when DotNetNuke is being strange. I am running 10+ DNN sites at version 5.6.0 and I only encountered this issue once.
I know this has some crossover to Serverfault.com but the advice on meta.stackoverflow was to ask it here (first) as it requires a .NET dev to answer more than likely.
I am having some problems publishing to my website a Click Once App, I am getting an error message saying (something like) IIS not running, I'm not currently at home to give an exact error message, i'll edit later if it is required to answer this question.
My ISP is lunarpages the plan I am on is this one IIS is definitely running as I have BlogEngine.NET running just fine. Anyone know what is required configuration wise (both server and client) to make this work?
The files that the ClickOnce publish create can be run on just about any web environment (include Apache/Linux.) It simply generates an html page along with the application manifest and your application files. Maybe you can deploy to a local folder and upload the files to the server?