[Resolved with 1.7.4+] Web SDK / Web Client from browser: 403 Forbidden

Hey @ZoomFan,

Stay updated here: https://marketplace.zoom.us/docs/changelog

We should have the release rolling out in the next day.

Thanks,
Tommy

Hey @rick2,

No timeline yet for higher quality video streams, but it is in our backlog.

Thanks,
Tommy

Because it is now mandatory for people to login to use the web client we are experiencing a lot of problems. It now redirects all users that want to use the web client to our company SSO login page(Azure AD). But external users don’t have an account within our company.

Using the desktop client is not always an alternative, because at some companies they are not allowed to install client. So this makes the product useless for most external meetings.

Is there any timeline when this will be fixed?

1 Like

Hey @meijndert,

For Web Client inquires please reach out to support.zoom.us as the Web Client is not apart of the Zoom Developer Platform.

Thanks,
Tommy

Honestly, thats not much. We NEED a WebClient without Registration. This is our primary requirement for Zoom. We have a lot of problems right now with our customers, since we cannot use Zoom for any of our meetings&webinars since 4 days! We are talking about money vanishing right now as we speak! And there is no clear answer if this situation will be resolved. We are now forced to look for other video meeting solutions and leave Zoom because of this. It is incredibly how bad communication is on this topic, and how this takes a wrong direction against the needs of your customers.

Hi everyone,

The Web SDK is now operational, we’ve released Web SDK version 1.7.4. Please see the thread below for more details.

Thanks
#codeHappy

hello,
are you sure is now operational?
fresh clone websdk 1.7.4
cd Local
npm i
npm run start (i remove --open flag otherwise the build failed)
Launch an instant meeting from zoom client
In browser put the meeting number and try to join
In the client click on admit new participant
then in browser the meeting page showing about 3sec
and then the modal box with message
Your connection has timed out and you cannot join the meeting. Verify your network connectivity and try again.
So what?
No happy code but quite frustrating since 03 april
fky

1 Like

@franckysolo same issue for me. Appreciate Zoom effort (it must be like hell right now!) but it seems that the new sampleapp is not fully functional yet.

1 Like

@gabriele.limonta yes you’re right but there’s lot of many people who paid for a service, developers who have deadlines, and it’s hell for zoom customers too!

Well, it seems to work for me, but i have a problem with it wich i didnt have before.

Now, if theres noone on the meeting, when trying to join via the sdk, i get the messaging saying that the meeting have not started yet, even if joining before the owner is alowed.

If i join by the meeting link on the web, or the other apps and then i try to join from my sdk implementation, it joins without problem.

I’ve made it works by adding a field meeting_email in index.html and the meeting_email value to meetConfig

document.getElementById('join_meeting').addEventListener('click', (e) => {
    e.preventDefault();

    const meetConfig = {
        apiKey: API_KEY,
        apiSecret: API_SECRET,
        meetingNumber: parseInt(document.getElementById('meeting_number').value, 10),
        userName: document.getElementById('display_name').value,
        userEmail: document.getElementById('meeting_email').value,
        passWord: document.getElementById('meeting_pwd').value,
        leaveUrl: 'https://zoom.us',
        role: parseInt(document.getElementById('meeting_role').value, 10)
    };

    ZoomMtg.generateSignature({
        meetingNumber: meetConfig.meetingNumber,
        apiKey: meetConfig.apiKey,
        apiSecret: meetConfig.apiSecret,
        role: meetConfig.role,
        success(res) {
            console.log('signature', res.result);
            ZoomMtg.init({
                leaveUrl: 'http://0.0.0.0:9999',
                success() {
                    ZoomMtg.join(
                        {
                            meetingNumber: meetConfig.meetingNumber,
                            userName: meetConfig.userName,
                            userEmail: meetConfig.userEmail,
                            signature: res.result,
                            apiKey: meetConfig.apiKey,
                            passWord: meetConfig.passWord,
                            success() {
                                $('#nav-tool').hide();
                                console.log('join meeting success');
                            },
                            error(res) {
                                console.log(res);
                            }
                        }
                    );
                },
                error(res) {
                    console.log(res);
                }
            });
        }
    });
});

But i’m not sure if it really fix it!
Maybe could have staff infos!
fky

I got it work after creating new conference, old ID’s are not worked.

Hi @franckysolo, Yes, please make sure that the meeting IDs exist, or you could create a new one to test out.

When we try to start a meeting using WebSDK 1.7.4, we get an error in the console
errorCode: 403
errorMessage: “The service is temporarily”
method: “join”
result: null
status: false

Hi Michael,
thanks for your team works and for reply
i try with my instant meeting number, with my simple account just for development
so yes the meeting id exist
With the simple account i can’t modify instant meeting number
i will try to create another one to test it
and told to you

I have account, that worked with 1.7.2 and after update nothing work.

Last response from server brings message
/**/localJsonpCallback({"status":false,"errorCode":-1,"errorMessage":"Unknown error.","result":null});

1 Like

Hi @ttodorov,

I’ll DM you a meeting ID to try out. It could be either invalid meeting ID, password or email variable config issue.

try to create new conference, and don’t leave any variable blank

1 Like

@michael_p.zoom yes please.

With provided ID all is working correctly. But with generated ID manually by REST SDK is not good. May be some options are required or some are exceed.