Getting "404 Not Found" When I configure new OBI200
RFC3261:
Quote from: hzct on May 17, 2018, 06:22:58 pm
I believe this is web server capacity problem.
Possible, but the nginx web server (which is what the openresty packaging uses under the covers) typically produces different errors than 404 (not found) under excessive loads, and the obi infrastructure is mostly run on AWS, which has various scaling capabilities (load balancers and/or very large instance types) which would suggest simple capacity is not the issue. I do agree with chilirock that we are unlikely to know the root causes, it will just eventually get different (hopefully better).
CoasterDean:
The plot thickens (see my previous post above).....
As I've been doing for the past few days, I try each morning to connect GB to my Obi 200. For some reason, it actually worked this morning. I went through the process as I always have, but I got no 404 error. GV shows up in SP1 and states that it's connected. When I get home tonight, I'll do a full test with the GV phone number, test the voicemail, etc.
So if you've been having the 404 problem, go and give it a shot. It might work for you now.
chilirock:
I tried again tonight and I was able to successfully add a secondary Google Voice account to my Obi200. The setup completed as normal without errors. Here's hoping the issue has been resolved.
It is disconcerting that there can be a serious production issue that prevents users from adding services to their new or existing devices and there is no communication from the company that sold and supports the device.
Navigation
[0] Message Index
[*] Previous page