Sudden Inability to Post to any HTTP Endpoint with Fetch: Pipedream Certs are Invalid

Help
,
1

Suddenly this morning, all our Fetch requests to HTTP endpoints in Pipedream just fail. This has never happened and we have not changed any of our code. So for example the request below fails with a strange error: ERR_CERT_COMMON_NAME_INVALID, and the fetch request never gets started. We have not changed anything in our code whatsoever, and the fetch has worked for months already, and just started failing this morning. From the error, it appears that the Pipedream SSL at the endpoints is inaccurate? Our endpoints are of the form: https://.m.pipedream.net. And if we visit the http endpoints directly in the browser we get the following message: Your connection is not private. The https warning also says that the SSL cert on pipedream is invalid.

const url = new URL('<HTTPENDPOINT>');
       
          const res = await fetch(url.toString(), {
            method: 'POST',
            body: JSON.stringify({ token, email, id }),
            headers: {
              'Content-Type': 'application/json',
            },
          });
2

Hi @osseonews

I’m not seeing this error on any of my own HTTP triggered workflows, and they have the same URL naming convention.

That error indicates some kind of SSL issue, can you share an instance of an endpoint that’s causing you this error?

Is it possible you’re using a VPN or some kind of tunnel that’s affecting your HTTP traffic?

3

Hi there,
We are not using any sort of VPN. We are just connecting via a regular Internet connection and using Chrome. Chrome issue a warning that https:// …pipedream.net is not private and the SSL is invalid. Here is the URL to an endpoint I just created for a blank workflow. Same error: https://eocbb7ossyngk3o.m.pipedream.net/ - visiting this URL in the browser, throws an SSL error for us.

4

Hi @osseonews

I just visited the URL and the HTTPS connection works for me:

CleanShot 2022-10-11 at 09.36.50@2x
CleanShot 2022-10-11 at 09.36.50@2x964×328 21.4 KB

Perhaps try an incognito window? Is it possible some Chrome extension is interfering with your traffic?

5

It doesn’t work in inconito window either. We don’t have any chrome extensions that interfere. What’s strange is that this just started happening this morning. We have never seen this before.

6

Just connected/re-routed traffic thru another internet provider and it worked. Is it possible that some service providers are blocking the connection? I’ve never seen this before.

7

We’ve had issues with Eero network gear outright blocking the Pipedream.com domain before, but not modifying SSL certs.

Which ISP where you using when you were experiencing this issue?

8

Verizon

9

Thanks for letting us know, we’re just trying to reproduce. We tried a mobile phone with a Verizon plan but again the URL loads and the SSL connection is established just fine.

Are you using a Verizon home / business cable connection?

10

Yes, Verizon home. Verizon mobile works. I’ll test some more later myself.

11

Verizon Fios.

12

@osseonews Could you do us a favor and reach out to Fios support to see if they can provide details on the issue? The certificates on *.m.pipedream.net domains are valid, so it would be good to have someone from the Fios side dig into it. If you’re able to reach someone via email, feel free to CC support@pipedream.com so we can provide any necessary information from our end.

13

@osseonews another follow up question - what kind of router do you have? Just would like to rule that out as well.