Answers: <p>Thaks for all answers. 
  Teamcity began to work correctly when I installed all windows updates to my Windows Server 2012 R2. 
  Maybe it depended with last Microsoft security update.</p>
  
Answers: CC BY-SA 4.0
Answers: 2018-05-14T10:10:55.607Z
Answers: 2018-05-14T10:10:55.607Z
Answers: kazakov.nickolay
Body: <p>I have Teamcity on Windows machine.<br>
  When installed it, I selected the 8080 port.<br>
  I have another application on the 80 and 443 ports.<br>
  It worked fine, but now I see an error:</p>
  
  <p><a href="https://i.sstatic.net/mAsNB.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/mAsNB.png" alt="enter image description here"></a></p>
  
  <p>But if I open <code>localhost:8080</code> on a virtual machine - all works well.</p>
  
  <ol>
  <li>What happened? Maybe you know :(</li>
  <li>How I can change port or change working to "without SSL"?</li>
  <li>How I can move all my projects to another Teamcity?</li>
  </ol>
  
  <p>Thanks!</p>
  
Comments: CC BY-SA 4.0
Comments: 2018-05-11T12:05:06.313Z
Comments: for your 2) just use http:// instead of https:// (which is likely your problem)
Comments: Tensibai
Comments: CC BY-SA 4.0
Comments: 2018-05-11T12:38:44.947Z
Comments: @Tensibai it is not working. Auto redirect to https http://nuget.b2bfamily.com:8080/
Comments: kazakov.nickolay
Comments: CC BY-SA 4.0
Comments: 2018-05-11T12:42:45.580Z
Comments: Then sorry, but the message being what it is, the SSL configuration (either the certificate or the listener configuration, or whatever to be guessed somewhere in your installation) is invalid. May worth trying with another browser, but I'm unsure this would change the result.
Comments: Tensibai
Comments: CC BY-SA 4.0
Comments: 2018-05-13T15:13:55.780Z
Comments: I agree with @Tensibai, you probably have to use non-HTTPs. You're on Firefox; it and Chrome auto redirect to HTTPS. I have to use Vivaldi for projects I know aren't configured with SSL
Comments: BoomShadow
Comments: CC BY-SA 4.0
Comments: 2018-05-14T10:07:50.763Z
Comments: Thaks for all answers. Teamcity work correctly when I installed windows updates. Maybe it depended with last microsoft security update.
Comments: kazakov.nickolay
Tags: <windows><teamcity>
Title: Teamcity web-interface does not work
UserDisplayName: kazakov.nickolay
ThreadText: # Teamcity web-interface does not work
  
  (Asked by: username_0 on 2018-05-11)
  
  I have Teamcity on Windows machine.  
  When installed it, I selected the 8080 port.  
  I have another application on the 80 and 443 ports.  
  It worked fine, but now I see an error:
  
  [![enter image description here](https://i.sstatic.net/mAsNB.png)](https://i.sstatic.net/mAsNB.png)
  
  But if I open `localhost:8080` on a virtual machine - all works well.
  
  1. What happened? Maybe you know :(
  2. How I can change port or change working to "without SSL"?
  3. How I can move all my projects to another Teamcity?
  
  Thanks!
  
  **Tags:** windows, teamcity
  
  > **Comments:**
  > **username_1**: for your 2) just use http:// instead of https:// (which is likely your problem)  
  > **username_0**: @username_1 it is not working. Auto redirect to https http://nuget.b2bfamily.com:8080/  
  > **username_1**: Then sorry, but the message being what it is, the SSL configuration (either the certificate or the listener configuration, or whatever to be guessed somewhere in your installation) is invalid. May worth trying with another browser, but I'm unsure this would change the result.  
  > **username_2**: I agree with @username_1, you probably have to use non-HTTPs. You're on Firefox; it and Chrome auto redirect to HTTPS. I have to use Vivaldi for projects I know aren't configured with SSL  
  > **username_0**: Thaks for all answers. Teamcity work correctly when I installed windows updates. Maybe it depended with last microsoft security update.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-05-14. Score: 1 | Accepted answer
  
  Thaks for all answers.
  Teamcity began to work correctly when I installed all windows updates to my Windows Server 2012 R2.
  Maybe it depended with last Microsoft security update.
  
  
  ---
  
  