-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On-prem exchange #3
Comments
Could you hit F12 in the browser window and post the "Console" section of the browser log? Thanks. |
http://localhost:8080/socket.io/?EIO=3&transport=polling&t=L_6HJMm net::ERR_CONNECTION_REFUSED |
I will try and look at my old code tomorrow and see if there's anything that can help there. Previously, I had this working with on-prem 2010 SP2. Did you attempt to change the port of the server at all? |
I have the exact same issue. On-prem Exchange 2013. Website with roomlists is visible, but not clickable. No information is shown. No ports were changed |
@clausmoell @yscotty A few more things--I apologize for all the unknowns as I didn't have multiple environments to test this:
|
Hi Dan
If I try in connect to the ubuntu IP:8080 from a domain computer I get a lot of the above net::ERR_CONNECTION_REFUSED as yscotty also experiences. I've also tried installing a GUI on the Ubuntu and connecting to localhost:8080 in a browser. This time I don't get the net::ERR_CONNECTION_REFUSED - but I get this output in the Developer Console: react-dom.production.min.js:163 TypeError: Cannot read property 'map' of null |
Yes, sorry. Fresh Ubuntu build. 8080 port. One primary domain. |
Also having the same issue. Single domain also on Ubuntu 16.04. Not using IIS. |
Is it resolved? Recently, I am looking for a solution to better manage our meeting rooms and we're planing the Exchange system. |
Not sure if its related.. I just tried it and noticed a 401 error. Its trying to use Basic Authentication which has been disabled on the onprem server as it is insecure.. Not sure if this can be changed to use something more robust ? |
@danxfisher I'm running Exchange 2013 CU21 and MeetEasier shows a warning: Oops, there seems to be an issue with the credentials you have supplied. Make sure you typed them correctly and that you have access to Exchange Roomlists. I can logon using the same credentials on OWA and see al the meeting rooms. |
Did you resolved for onprem @nvdlsl |
I took the advise of the reddit post and attempted this with our on-prem exchange (both 2013 and 2016 servers) just to see if it works (and for fun).
Changing "var exch = new ews.ExchangeService(ews.ExchangeVersion.Exchange2016);" to accommodate either 2013 or 2016 EWS setups did seem to get it to work somewhat. I tried both 2013 and 2016 server EWS uri's. It works "up to a point".
The terminal console of my ubuntu server starts showing all the rooms and roomlists as I refresh the website in a browser.
And I can see the room lists show up in the website. But that's all I get. The roomlists aren't clickable. No information is shown. I just get a page with a drop down of all my room lists.
Figured I'd put this here in case someone else was chancing it with on-prem servers or had similar issues.
Auth all seems in order, and I can't see any errors to report. shrug
The text was updated successfully, but these errors were encountered: