Forum Discussion
WAC 1808 File Copy errors and powershell disconnecting...
MicrosoftPlease check out the troubleshooting guide for common issues and resolution steps. If nothing there solves your issue, please reply back here with the answers to the troubleshooting common questions.
For the PowerShell issue, please confirm if the Events and Remote Desktop tool work, the issue you describe occurs when something is blocking websockets in your environment.
For the file upload issue - please also include:
- Size of the file you are trying to upload
- Local path of the source file
- Remote destination path
Thank you for replying. I tried to apply suggested changes. We are talking about version 1809 now (after upgrade from 1808). Initially after accessing site I was indeed getting error message websocket/powershell could not connect. I checked features on Server 2016 and added WebSocket feature. Now I am not able to connect to server even locally getting connection refused message. On the other WACs (using version 1808) I am able to both view the events and trigger RDP session. However Powershell disconnect immediately.
Any thoughts?
Thank you
- Jeff Woolslayer
There is no WebSocket feature in Windows server. Practically all WebSockets compatibility issues are caused by the network environment (proxy servers, firewalls, etc..)
Please create an item for your upload issues here for ease of tracking: https://aka.ms/wacfeedback
Hi Jeff Woolslayer There is a feature for a WebSocket withing Web Server / Application Development however installing it made no difference. The link provided just takes me to Microsoft site. Is there any more detailed how to's regarding WAC? I see a lot of potential but practical usage is a different story. Any steps I can do for troubleshooting? Of course completely disabling firewall and "opening the shop" is out of question but is there a way to adjust more finely error handling in order to make it work?
- Jeff Woolslayer
Thanks for the clarification on the role! Unfortunately, the WebSocket Protocol role feature under IIS\Web Server\Application Development is for enabling it on IIS websites. The HTTPS listener created by WAC does not use IIS.
Since WebSocket compatibility can be impacted by any device that routes or filters network traffic in your environment, there is no definitive guide to configuring it. I can assure you that you it is possible to support WebSockets in an environment without completely disabling firewall and "opening the shop."
We have only seen WebSocket compatibility issues reported by a small subset of users, and have yet to identify any common root cause. I'm continuing to track this, and will update this location in our documentation with any new information: https://aka.ms/wacwebsockets
