Mobile Push Stopped Working

45 views

Skip to first unread message

bon lis

unread,

Feb 10, 2025, 4:47:51 AMFeb 10

to RCDevs Security

Hello, After updating WEBADM to version 2.4.0-2 and OPENOTP to version 2.2.24-1, MOBILE PUSH stopped working. Before the update, I didn't use WAPROXY and it worked. Is there anything new in this version? Do I have to set up WAPROXY in my DMZ now?

Spyridon Gouliarmis (RCDevs)

unread,

Feb 10, 2025, 4:50:49 AMFeb 10

to RCDevs Security

Hello, I assume you were using the cloud_wsproxy setting. What is its value now, in webadm.conf?

bon lis

unread,

Feb 10, 2025, 6:00:27 AMFeb 10

to RCDevs Security

the value is cloud_wsproxy: yes

It's been working this way for years without any problems, but after the last update it stopped working.

Spyridon Gouliarmis (RCDevs)

unread,

Feb 10, 2025, 8:00:32 AMFeb 10

to RCDevs Security

Our cloud is not running wsproxy at the moment, and we're still investigating why. We expect it to be resolved tomorrow. It's still a bit early for the feature to be stable (the changelog does say it's still in beta).

To be sure that WebADM picks up the setting properly, can you check the values for OpenOTP's Mobile Token URL in the Applications tab? They should start with https://cloud.rcdevs.com .

If you've been using push notifications without a reverse proxy for years, as you write, and since cloud_wsproxy is a months-old feature, I can only assume push notifications were working because your smartphones were on your local wifi and could answer to WebADM directly. If that's the case, you can go back to not using the wsproxy feature.

Reply all

Reply to author

Forward

0 new messages