Bug #2
Updated by Vincent Rubiolo over 1 year ago
When trying to create a new app in an existing project through redpesk UI, step 3 (Choose add method) fails when selecting "# Add Sample App / Helloworld binding". Reason for failure is "408 Request Time-out" (please see attached screenshot).
# Debugging information
Gathered from various spots/sessions/conversations and centralized here:
## 2022-04-10
- with Emmanuel's machine (OpenSuse VM via Virtualbox on a Windows host)
- using his phone Wifi hotspot (Free network), application creation fails
- on the SAFT network, application creation succeeds (i.e. the problem does not occur)
- using Frederic's phone Wifi hotspot (Orange network), application creation succeeds
- with Frederic's Mac machine using the same OpenSuse VM (via Virtualbox) and the SAFT network, application creation works
Based on the information above, it looks like a particular behavior with the Free mobile network which might be filtering certain network packets when using a Wifi hotspot
## 2022-04-01
Emmanuel mentions that creation via `rp-cli` works fine.
## 2022-09-22 debugging session
- with Emmanuel's machine (OpenSuse VM via Virtualbox on a Windows host) on Emmanuel's phone (Android on the Free mobile network)
- changing the Wireguard MTU to 1416 in the OpenSuse VM does not change anything
- Emmanuel mentions that he had the same issue on a native OpenSuse distribution running the Wireguard client (his own machine)
- this rules out an interaction between the VM/hypervisor in Windows and the Wireguard client
- Request type
- application creation uses a `PUT` request and fails (request size = 1089 bytes, as shown via `curl -w '%{size_request} %{size_upload}'`
- same is true for project creation/save
- editing the user's profile (changing the telephone number) also uses `PUT` but does _NOT_ fail
- doing a build (via a `POST` request) works fine
- using `curl` instead of the UI for saving an application/project settings works fine
- this works fine whether this is using a token or a session ID
- Emmanuel also sees a similar `408 Timeout` issue when trying to use Chrome to log into the stack (`GET` request)
## TODOs Potentially to test:
- Emmanuel
- with Emmanuel's other wife phone: also on the Free mobile network but with a different Android version (purpose: rule out Android interactions)
- retry with native OpenSuSe machine w/ Wireguard client (purpose: rule out Windows/Virtualbox interactions)
- IoT.bzh
- try the same setup as Emmanuel (Wifi connection sharing over Free network)