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
-------- DO NOT EDIT --------
OS Version: 6.1.57-android14-11-g2de3ba70f288-ab11985038(V816.0.27.0.UNNCNXM)
OS API Level: 34
Device: rothko
Model (and Product): 2407FRK8EC (rothko)
Application version: 5.9.18-foss
Crashlytics UID: null
Provide bug details
Without making any changes to the configuration, I exported the configuration information and found the rpc-listen-port and serverToken.
But after filling them into AriaNg, the connection failed.
I have tried P9D=Vr:\ and P9D=Vr:, and it's not a problem with the escape character.
Additionally, I found that modifying the content of Figure 1 and re-uploading it is ineffective, which means that if the rpc-listen-port and rpc-secret in the In-App-downloader settings are changed, it will not start properly (I have indeed tried this).
The text was updated successfully, but these errors were encountered:
I'm starting to get confused because I've discovered that the HTTP protocol is not allowed, while the WS protocol can be used normally.
Due to the fact that Alist and some browser extensions only support sending a single download request to Aria via the HTTP protocol, their functionality has been rendered ineffective. However, I recall that the WS protocol was clearly developed based on the HTTP protocol, so how could this be the case?
-------- DO NOT EDIT --------
OS Version: 6.1.57-android14-11-g2de3ba70f288-ab11985038(V816.0.27.0.UNNCNXM)
OS API Level: 34
Device: rothko
Model (and Product): 2407FRK8EC (rothko)
Application version: 5.9.18-foss
Crashlytics UID: null
Provide bug details
Without making any changes to the configuration, I exported the configuration information and found the rpc-listen-port and serverToken.
But after filling them into AriaNg, the connection failed.
I have tried P9D=Vr:\ and P9D=Vr:, and it's not a problem with the escape character.
Additionally, I found that modifying the content of Figure 1 and re-uploading it is ineffective, which means that if the rpc-listen-port and rpc-secret in the In-App-downloader settings are changed, it will not start properly (I have indeed tried this).
The text was updated successfully, but these errors were encountered: