I will update that information to say it requires mojoPortal 220.127.116.11, sorry for any inconvenience.
Sorry for the inconvenience. I was worried about breaking other people's custom code by updating to the new log4net because I thought it might require everyone to re-compile their custom features against the new log4net dll, but I was able to prevent that problem by adding this in the Web.config in 18.104.22.168:
<assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="22.214.171.124-126.96.36.199" newVersion="188.8.131.52" />
though it still would be best for anyone using custom code that also uses log4net to re-reference it and re-compile when they get a chance.