You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we are running OpenMeetings 6.1.0 on RHEL7 behind an Apache Web Server reverse proxy for HTTPS termination.
We are observing an issue where items in the UI that would spawn a modal box (such as clicking the About link on the dashboard or attempting to use the invite functionality in a meeting room) will cause the dialog to fail to appear (although the page is darkened to indicate that a box should appear).
In other cases, such as when opening the settings menu within a meeting room, we are able to open the modal dialog box, but the box then refuses to close regardless of what buttons are pressed. The only way to clear the box in that instance has been to refresh the page.
We have observed this issue in both Chrome and Firefox, and have tried removing the Apache Web Server proxy to see if it was an issue with the proxy, and still observed this issue.
The text was updated successfully, but these errors were encountered:
the issue like this was reported multiple times, but unfortunately I'm unable to reproduce it :(
The most promising report was this one: https://markmail.org/message/pibnskpjuewndkqy
Hi, we are running OpenMeetings 6.1.0 on RHEL7 behind an Apache Web Server reverse proxy for HTTPS termination.
We are observing an issue where items in the UI that would spawn a modal box (such as clicking the About link on the dashboard or attempting to use the invite functionality in a meeting room) will cause the dialog to fail to appear (although the page is darkened to indicate that a box should appear).
In other cases, such as when opening the settings menu within a meeting room, we are able to open the modal dialog box, but the box then refuses to close regardless of what buttons are pressed. The only way to clear the box in that instance has been to refresh the page.
We have observed this issue in both Chrome and Firefox, and have tried removing the Apache Web Server proxy to see if it was an issue with the proxy, and still observed this issue.
The text was updated successfully, but these errors were encountered: