Select to view content in your preferred language

Notebook Websocket Issues

595
1
Jump to solution
03-18-2024 08:47 AM
CodyPatterson
MVP Regular Contributor

Hey All,

Enterprise 11.2, Most recent Python Containers & Images

Recently, I've experienced quite a few issues regarding the ArcGIS Notebook and connecting through out reverse proxy. We are getting constant WebSocket issues after changing the DNS name of our reverse proxy address. I was curious if anyone has an example of this here:

CodyPatterson_0-1710776615971.png

I was not able to replicate this, and I believe the documentation is very outdated, even though it is for 11.2.

Here are the errors I am getting:

CodyPatterson_1-1710776697680.png

 

There are no insights offered by Google Chrome WebSocket view or Firefox. Wireshark so far has not shown anything great, but my assumption would be that it is currently being stopped at the reverse proxy, and not able to pass through.

Also just a note, this worked in 11.1, but after an upgrade to 11.2, it stopped.

Thanks in advance!

1 Solution

Accepted Solutions
CodyPatterson
MVP Regular Contributor

Hey all,

Somehow we have resolved this, it seemingly has been related to the rewriting of web sockets as was originally thought. The ESRI documentation was not helpful, and provided no insight into the issue, I ended up just working for hours against this and only this. This is what resolved it once I placed it into my reverse proxy:

    RewriteEngine On
    RewriteCond %{HTTP:Connection} Upgrade [NC]
    RewriteCond %{HTTP:Upgrade} websocket [NC]
    RewriteRule /(.*) wss://<FQDN of machine (Not reverse proxy)/$1 [P,L]

Example:

    RewriteEngine On
    RewriteCond %{HTTP:Connection} Upgrade [NC]
    RewriteCond %{HTTP:Upgrade} websocket [NC]
    RewriteRule /(.*) wss://https://arcgisnotebook.company.local/$1 [P,L]

 

I sincerely hope this helps someone in the future, as we have struggled with this for months.

Cody

View solution in original post

1 Reply
CodyPatterson
MVP Regular Contributor

Hey all,

Somehow we have resolved this, it seemingly has been related to the rewriting of web sockets as was originally thought. The ESRI documentation was not helpful, and provided no insight into the issue, I ended up just working for hours against this and only this. This is what resolved it once I placed it into my reverse proxy:

    RewriteEngine On
    RewriteCond %{HTTP:Connection} Upgrade [NC]
    RewriteCond %{HTTP:Upgrade} websocket [NC]
    RewriteRule /(.*) wss://<FQDN of machine (Not reverse proxy)/$1 [P,L]

Example:

    RewriteEngine On
    RewriteCond %{HTTP:Connection} Upgrade [NC]
    RewriteCond %{HTTP:Upgrade} websocket [NC]
    RewriteRule /(.*) wss://https://arcgisnotebook.company.local/$1 [P,L]

 

I sincerely hope this helps someone in the future, as we have struggled with this for months.

Cody