We encountered an issue where the umbraco.config cache file was not being updated by publishing content, the timestamp is not altering.
I thought I should share the solution.
We had to forceProtocol and forcePortnumber for the server (not sure what the default is) but I set them to http and 80 and it works again. these settings in the /config/umbracoSettings.config
Not sure it's actually a bug, because if your site runs SSL, Umbraco will try to ping the webservices over SSL as well (which you can then override using the new config above).
Yes, that does make sense, I wasn't sure it was a bug either, however it did take me a while to figure out the solution, hence this thread... and I'm guessing my scenario where the authoring server has SSL but none of the web serverers have SSL will be a common setup, so others may run into the same thing.
umbraco.config not updating with distributedCall
We recently upgraded a site from v4.7.0 to 4.7.2
We encountered an issue where the umbraco.config cache file was not being updated by publishing content, the timestamp is not altering.
I thought I should share the solution.
We had to forceProtocol and forcePortnumber for the server (not sure what the default is) but I set them to http and 80 and it works again. these settings in the /config/umbracoSettings.config
<distributedCall enable="true"> <server forceProtocol="http|https" forcePortnumber="80|443">127.0.0.1</server>This is definitely a bug, so could you log it on Codeplex and I'll make sure it gets resolved for 4.8.
ok, done:
http://umbraco.codeplex.com/workitem/30901
Note: our solution has umbracoUseSSL="true" in the web.config, however, I'd still expect nonSSL to be the default :-)
Not sure it's actually a bug, because if your site runs SSL, Umbraco will try to ping the webservices over SSL as well (which you can then override using the new config above).
Yes, that does make sense, I wasn't sure it was a bug either, however it did take me a while to figure out the solution, hence this thread... and I'm guessing my scenario where the authoring server has SSL but none of the web serverers have SSL will be a common setup, so others may run into the same thing.
is working on a reply...