Welcome Guest! To enable all features please try to register or login.
Options
Go to last post Go to first unread
Offline Chanh  
#1 Posted : Wednesday, November 6, 2019 10:48:15 AM(UTC)
Chanh

Rank: Newbie

Reputation:

Groups: Registered, Registered Users, Subscribers
Joined: 11/5/2019(UTC)
Posts: 0

I am having a problem on how to run Oqtane in IIS.

I tried to do the publish to a folder and copy the "publish" folder in IIS but it just shows blank screen rather than the Oqtane front page.

Any idea?

Thanks
Offline Chanh  
#2 Posted : Friday, November 8, 2019 1:40:49 PM(UTC)
Chanh

Rank: Newbie

Reputation:

Groups: Registered, Registered Users, Subscribers
Joined: 11/5/2019(UTC)
Posts: 0

This is the error that I was able to capture in IIS.

blazor.server.js:1 [2019-11-08T21:34:35.417Z] Information: Normalizing '_blazor' to 'http://localhost:83/oqtane/_blazor'.
blazor.server.js:1 [2019-11-08T21:34:35.492Z] Information: WebSocket connected to ws://localhost:83/oqtane/_blazor?id=0F275OoiHomg78CNkiOOrA.
blazor.server.js:15 [2019-11-08T21:34:35.514Z] Error: There was an unhandled exception on the current circuit, so this circuit will be terminated. For more details turn on detailed exceptions in 'CircuitOptions.DetailedErrors'.
e.log @ blazor.server.js:15
S @ blazor.server.js:8
(anonymous) @ blazor.server.js:8
(anonymous) @ blazor.server.js:1
e.invokeClientMethod @ blazor.server.js:1
e.processIncomingData @ blazor.server.js:1
connection.onreceive @ blazor.server.js:1
i.onmessage @ blazor.server.js:1
blazor.server.js:1 [2019-11-08T21:34:35.516Z] Information: Connection disconnected.

Any idea what is missing that causes this error?

Thanks
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF.NET | YAF.NET © 2003-2019, Yet Another Forum.NET
This page was generated in 0.311 seconds.

Notification

Icon
Error