Answers.Body: <p>Figured it out. Config was set to force https, but the new server didn't have an ssl certificate set up. Fixing that cleared up the issue.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-02T14:19:06.857Z
Answers.LastActivityDate: 2017-05-02T14:19:06.857Z
Answers.UserDisplayName: artmem
Body: <p>I just moved a site over to a Windows server, and my homepage loads fine, but sub pages are not loading. I just get an error message that the connection was reset. Adding index.php to the url doesn't do anything.</p>
  
  <p>My control panel is also loading fine, it's just the sub-pages.</p>
  
  <p>I don't really have any experience with Windows servers, so I'm not sure how to go about troubleshooting this. I'm using the standard craft web.config file. Is there a config setting I need to add?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-01T15:53:12.333Z
Comments.Text: What files did you move over? You might try clearing Craft's cache files (Settings -> Clear Caches) since Craft's caches rely on folder paths. If you're now on a different server/OS those paths will be different.
Comments.UserDisplayName: RitterKnight
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-01T16:00:34.047Z
Comments.Text: @RitterKnight  I moved over all files. Cleared caches and rebuilt image and search indexes. Same results.
Comments.UserDisplayName: artmem
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-01T16:10:17.673Z
Comments.Text: Do you have access to the IIS error / event log? That should help determine why exactly the connection is being reset.
Comments.UserDisplayName: RitterKnight
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-01T16:50:29.543Z
Comments.Text: @RitterKnight I don't have access to the error log.
Comments.UserDisplayName: artmem
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-01T19:31:37.413Z
Comments.Text: @artmem It's probably a 500 ISE error and the underlying error is probably in the IIS error logs / Windows event viewer. Maybe have your host look into the logs or at the least give you access to them?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-02T14:18:45.807Z
Comments.Text: Figured it out. Config was set to force https, but the new server didn't have an ssl certificate set up. Fixing that cleared up the issue.
Comments.UserDisplayName: artmem
Tags: <server><installation><windows>
Title: Sub-pages not loading on Windows server
ThreadText: # Sub-pages not loading on Windows server
  
  (Asked by: username_0 on 2017-05-01)
  
  I just moved a site over to a Windows server, and my homepage loads fine, but sub pages are not loading. I just get an error message that the connection was reset. Adding index.php to the url doesn't do anything.
  
  My control panel is also loading fine, it's just the sub-pages.
  
  I don't really have any experience with Windows servers, so I'm not sure how to go about troubleshooting this. I'm using the standard craft web.config file. Is there a config setting I need to add?
  
  **Tags:** server, installation, windows
  
  > **Comments:**
  > **username_1**: What files did you move over? You might try clearing Craft's cache files (Settings -> Clear Caches) since Craft's caches rely on folder paths. If you're now on a different server/OS those paths will be different.  
  > **username_0**: @username_1  I moved over all files. Cleared caches and rebuilt image and search indexes. Same results.  
  > **username_1**: Do you have access to the IIS error / event log? That should help determine why exactly the connection is being reset.  
  > **username_0**: @username_1 I don't have access to the error log.  
  > **username_2**: @username_0 It's probably a 500 ISE error and the underlying error is probably in the IIS error logs / Windows event viewer. Maybe have your host look into the logs or at the least give you access to them?  
  > **username_0**: Figured it out. Config was set to force https, but the new server didn't have an ssl certificate set up. Fixing that cleared up the issue.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2017-05-02. Score: 2 | Accepted answer
  
  Figured it out. Config was set to force https, but the new server didn't have an ssl certificate set up. Fixing that cleared up the issue.
  
  
  ---
  
  