Network problem running as Access Point

The GW does allow me configure DNS to No-IP, TZO or DynDNS.org.  I need to create a logon for those to configure it.  Tried setting up No-IP and had something wrong, the status said "wrong option".  

Strangely, WEBEX is now working correctly with my current setup of using two routers in serial and using wifi to my router.  I will try testing it with a GW connection later.

That said, I believe that this has been two issues all along.  I didn't use GoFundMe until after making the change to an Access Point, so I associated it with the WEBEX problem and related both issues to the AP.  In fact, GoFundMe worked on my home network when I originally created my accounts (which was after configuring the AP) and then stopped working after a few hours.  I originally thought that GFM had blocked me, but then discovered that it worked if I used my cellular network instead of my home network.

                           Access Point         Router           GW

WEBEX:                   NOK                 OK                ??

GFM:                        NOK                NOK            NOK

But GFM (reCaptura) works from Cellular network (multiple devices) and for a short time worked on home network Access Point.

                           Access Point         Router           GW

WEBEX:                   NOK                 OK              NOK

GFM:                        NOK                NOK            NOK

But GFM (reCaptura) works from Cellular network (multiple devices) and for a short time worked on home network Access Point.

WEBEX works from browser, but not from desktop client.  Sames as Access Point. GW performance is really bad (some distortion in voice quality), but Access Point was good.  I will look for anything that stands out between configuration of Router and GW.

Ok, I think I have more informaiton on reCaptura.  Just for some background, we have two friends in Mexico who are both dealing with COVID, so we have created some GFM accounts for them.  However, you can't receive funds from GFM with a Mexican bank account and we are having to use a US account.

Anyway, the point of this is that we have been experimenting with how to create the account and assign a benificiary.  I was using both GFM accounts from the same PC (and Gateway IP).  When you receive an invitation from GFM to accept being a benificariary, it opens the link in your browser...but if you were already "signed in" to GFM with a different account...I think this breaks something with reCaptura...or you get marked as a suspect IP or something.

They only reason I say this, is basically we just replicated the issue with someone else's PC/network and it seems this issue may not have been related to my AP or GW at all.  I have no idea how to fix it once it has occured.  It doesn't appear to be related to my GFM account, but does appear to be linked to my GW IP, because the same behavior exists on all of my devices but it works with the same devices on my cellular network.

Information from the Chrome Console

Tried providing a picture of the Chrome console, but here is the error text.  I reported this issue to GFM and am thinking they decided to block my IP.

sign-in:1 Access to fetch at 'https://api.gofundme.com/auth/v1/login/email' from origin 'https://www.gofundme.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

api.gofundme.com/auth/v1/login/email:1 Failed to load resource: net::ERR_FAILED

Authentication.min.js?v=32.39:1 Uncaught (in promise) TypeError: Cannot read property 'error' of undefined

    at Authentication.min.js?v=32.39:1

When I logon via cellular network I get this error, but I am allowed access:

GET https://www.gofundme.com/assets/svg/fa-icons.svg net::ERR_ABORTED 404

I still would like to find a solution to WEBEX though.

I changed DNS to 8.8.8.8 and it resolved the problem with the Webex Desktop Application.  Thank you!

Glad it was an easy fix!