Remote controle doesn't works on self hosted w2k19
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.1k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I have the problem bellow?:
Can be reproduced.
This happens on your hosted solution after used the script Publish.ps1
Describe the bug
When I published the remotely at my server with IIS 10, almost features works, including chat, however, when I try use the remote control I have the problem that still show me "asking for permission", and when I do a element inspection on the browser, I received the message bellow:
Could not load content for https://server-name/_content/Immense.RemoteControl.Server/src/ViewerHubConnection.ts (HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE)
I noticed that all files bellow the folder _content doesn't reached from blasor app.
To Reproduce
hosted the remotely on windows server 2019
Expected Behavior
when I did a rollback to version Remotely-2022.09.16.1006, that is the last version with agents and total compiled, that works totally on the same structure.
Windows Server 2019 (please complete the following information):
thanks and waiting for someone that could help me.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the deployment with Publish.ps1 on Windows Server 2019 and IIS 10, then inspect the missing _content/Immense.RemoteControl.Server/src/ViewerHubConnection.ts request. Compare the failing release with Remotely-2022.09.16.1006, where the same structure worked. Done means the _content files load in the Blazor app and remote control no longer remains at “asking for permission”.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100