Precise start error may be because of buffering
This commit is contained in:
parent
6ed937d9b6
commit
cc22abe17a
|
@ -18,7 +18,7 @@
|
||||||
<string name="warning_notif_content">NextPush is disconnected</string>
|
<string name="warning_notif_content">NextPush is disconnected</string>
|
||||||
<string name="warning_notif_description">Warn when NextPush is disconnected or an issue occured.</string>
|
<string name="warning_notif_description">Warn when NextPush is disconnected or an issue occured.</string>
|
||||||
<string name="warning_notif_ticker">Warning</string>
|
<string name="warning_notif_ticker">Warning</string>
|
||||||
<string name="start_error_notif_content">The service could not be started correctly. Check the configuration of your server.</string>
|
<string name="start_error_notif_content">The service could not be started correctly. Check the configuration of your server. You may be using a reverse proxy with buffering enabled.</string>
|
||||||
<string name="low_keepalive_notif_content">The server app is configured with a low keepalive: %ss. It will drain your battery. We recommend using a higher keepalive.</string>
|
<string name="low_keepalive_notif_content">The server app is configured with a low keepalive: %ss. It will drain your battery. We recommend using a higher keepalive.</string>
|
||||||
<string name="no_ping_notif_content">NextPush was disconnected 3 times before receiving the ping. You probably have a problem with your server configuration. Your reverse proxy timeout is probably too low.</string>
|
<string name="no_ping_notif_content">NextPush was disconnected 3 times before receiving the ping. You probably have a problem with your server configuration. Your reverse proxy timeout is probably too low.</string>
|
||||||
<string name="foreground_notif_ticker">Foreground</string>
|
<string name="foreground_notif_ticker">Foreground</string>
|
||||||
|
|
Loading…
Reference in New Issue