Microsoft Expression Web 4 No Longer Works

[brianc]

After my servers have been updated to v90, I am getting reports that Microsoft Expression Web 4 is no longer working. What changes were made in v90 that can explain this issue?

 

[PenguinInternet]

We've had a few similar reports and have confirmed this ourselves. When transferring files you get a message "Ready to proceed (200)" but you can't actually upload content.

 

[brianc]

We've had a few similar reports and have confirmed this ourselves. When transferring files you get a message "Ready to proceed (200)" but you can't actually upload content.

Is this only happening to your servers that have v90 installed on?

 

[cPanelLauren]

I'm unsure what portion of the software you're referring to doesn't work as it's not detailed here, is it the upload function that is causing the issue? Is there more than that? Does the program utilize FTP to upload?

I also noticed there's a service pack available for the software since April of this year https://support.microsoft.com/en-us/help/2571841/description-of-expression-web-4-service-pack-2

 

[brianc]

I'm unsure what portion of the software you're referring to doesn't work as it's not detailed here, is it the upload function that is causing the issue? Is there more than that? Does the program utilize FTP to upload?

I also noticed there's a service pack available for the software since April of this year https://support.microsoft.com/en-us/help/2571841/description-of-expression-web-4-service-pack-2

It is the upload feature that is causing the problems. It does upload by FTP but I think also by WebDav but I am not sure.

 

[brianc]

That service pack is no longer available either.

 

[cPanelLauren]

So something that changed in v90 is that the PureFTPd Package was updated if this is what you're using for your FTP server. There is a case open for issues with this but it does boil down to a change with PureFTPd and removal of support for the NLST command to perform globbing. This is noted here: Latest news :: Pure-FTPd

I'm unsure if that software only works with PureFTP or if it'll also be compatible with ProFTP but you may want to try using ProFTP to see if there are any changes in behavior

 

[jimhermann]

One of my sites is having the same problem. They confirmed that they are using SP2.

PureFTP released a new version. what version does cPanel 90 use?

jim

 

[cPanelLauren]

It's using the newest version, 1.0.49 which is why it was noted that this is the change in v90

 

[PenguinInternet]

For info, Webdav is supported by Expression Web and can be used as an alternative connection method in the absence of any FTP fix - we've been switching customers over to this method as a workaround as have confirmed that this works.

 

[cPanelLauren]

Thanks for that information @PenguinInternet are you aware if it encounters the same or similar issues when using ProFTPd?

 

[PenguinInternet]

We've just tried this on a test server and can confirm that when using ProFTPd, Expression Web does work without issues, however given the security compromises from this it wouldn't be my own choice to resolve the issue

 

[HarmW]

For info, Webdav is supported by Expression Web and can be used as an alternative connection method in the absence of any FTP fix - we've been switching customers over to this method as a workaround as have confirmed that this works.

I confirm the workaround, go to your CPanel and select Web Disk, that gives you the information needed to set the Connection Settings In Microsoft Expression Web 4.
Go to your CPanel and select Web Disk, that gives you the information needed to set the Connection Settings In Microsoft Expression Web 4.
In my case this works in MS Expression Web 4: Menu Site ; Publishing Settings; Add or Edit
Connection Type: WebDAV
Location: https : //mywebsite.nl:2078/public_html (without spaces).

 

[sneader]

Location: https : //mywebsite.nl:2078/public_html (without spaces).

@HarmW or anyone else -- do you happen to know the right format if a customer is publishing to an add-on domain? If their main domain is main.dom and their addon domain is addon.com (in the public_html/addon.com/ directory), would they use the format https://main.dom:2078/public_html/addon.com or https://addon.dom:2078/public_html/addon.com or something else? I do not have this software to test with, unfortunately.

- Scott