Have a look at the output results from something like fiddler - as i said - pretty sure its something to do with the port number not being attached correctly to the ajax callback url - if you can see what is going on with the actual urls - then please look at logging it as a support ticket - that way it will be looked at by dnn support crew.

Basically - look at fiddler - look for ajax call backs - look at the raw url - does it contain the correct domain - does it contain the correct port number?

https://dnntracker.atlassian.net/brow...  this ticket may be related but hard to say again without seeing actual results from your system.

Again I can give you any number of reasons why changing a port number when using ajax could generate issues - its all to do with how things are coded - what needs to be determined is which of the many possible ones are causing this.

Westa

Yeah friendly URL's was the other recommendation I saw to possibly fixing the issue but it did not have any impact. I removed the friendly and search safe Url's from the config and settings but it did not fix the issue in my case.

thanks for giving some ideas into fixing the problem.

We have at least a dozen applications using Ajax, MVC, friendly url's etc without any problems or special changes, I have no idea what's happening in DNN. May be some simple bit of logic in the portal alias manager or even in the BasicUrlRewriters.

I did notice that  I'm having more issues with the advanced URL's compared to the humanFriendly ones, where no messages are being displayed during ajax calls