Strange Redirect 404 (Probably nginx*)

Help Developers
1

Hello @cristi @dimitrie && @teocomi -

For some reason I’m getting a strange redirect error when logging in on a Speckle v2 instance we setup for a specific project.

See URL → https://speckle.centruscbr.ca

I get this 404 Error …

Screen Shot 2021-10-07 at 2.59.49 PM
Screen Shot 2021-10-07 at 2.59.49 PM1824×1624 120 KB

Yet, when I click ‘Home’ it actually takes me to my Speckle Dashboard??? Guessing this has something to do with a routing config or maybe nginx?

Screen Shot 2021-10-07 at 2.59.54 PM
Screen Shot 2021-10-07 at 2.59.54 PM1824×1624 158 KB

Some help is much appreciated.

2

Hi @markcichy ,

I created a test account ( Cristi - cristi@speckle.systems ) on the server you mentioned to try to reproduce, but I don’t get redirected to 404 page.

Can you tell where does it try to redirect? What’s the URL in the address bar in the 404 page?

Any errors in the JavaScript console?

1 Like
3

I can confirm, that it works as expected for me too.

4

Hey @markcichy, same - can’t reproduce - but since we replied late it may be that you fixed the problem :smiley:

5

So, funny story: it must be an internal routing issue. You are all correct, in that it works outside firewall as planned. When working within firewall it does not. Will have to ask our IT staff to analyze internal DNS.

Thanks for your help! Will delete your accounts now … :wink:

M

1 Like
6

Ah, @dimitrie — not so fast. :frowning:

It appear to work fine, HOWEVER, if you try to capture the Stream in Rhino or Grasshopper (or any client for that matter), login fails.

I am redirecting via Nginx to the internal machine IP in question. I’m wondering what the key ports are for Speckle. Obviously 443, but does 3000 still play a role? 80 would be the unencrypted internal port, which once traffic forwarded by Nginx would be encrypted. Confused, tired, and hoping there’s an obvious answer.

7

Hey @markcichy

Since you are using nginx for your internal redirect, you can check out our config at speckle-server/nginx.conf at main · specklesystems/speckle-server · GitHub

Long story short, there are a few routes we are proxying to the ${backend host}:3000

2 Likes
8

The solution was Let’s Encrypt root cert expiration as identified in this post by @teocomi / @dimitrie

Looks like this wasn’t entirely our fault? For once.

2 Likes
9

Thanks for the response. Glad it’s fixed :blush:

1 Like