-
Notifications
You must be signed in to change notification settings - Fork 39
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
SELF_URL_PATH is not recognized as environment variable #11
Comments
@x86dev
Another -e issue? I wonder if this is linked to my problem passing
variables.
…On Fri, Jul 14, 2017, 9:49 AM jcnoir ***@***.***> wrote:
Hi,
Thank you for this nice docker image.
I use it with the letsencrypt nginx proxy.
With the default configuration I cannot access the web page and I get an
error with incorrect SELF_URL_PATH.
I tried to set SELF_URL_PATH as an environment variable but it is not used.
I did workaround by passing these environment variables:
- TTRSS_URL=mysubdomain.mydomain.com
- TTRSS_PROTO=https
Setting the TTRSS_PORT as 443 does not work, I had to omit the value
(even if it is 443).
I don't know if it is a bug but it should be at least documented to avoid
debugging ...
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABzd_KYq7HthoWEyYKwEtKt-mLuJJnebks5sN3HFgaJpZM4OYRqm>
.
|
Same problem here! |
Some of the latest commits to TT-RSS contained some changes to SELF_URL_PATH. That was the reason why I extended / fixed the SELF_URL_PATH generation in the startup phase. For making this to work with e.g. https://github.com/jwilder/nginx-proxy, you also have to use -e VIRTUAL_HOST=<sub.yourdomain.tld> Just to be sure: You pulled the latest Docker image, right? |
To be sure I just pulled the latest version from the docker hub.
|
I'll have a look. |
I have the same problem (incorrect SELF_URL_PATH) ! |
The solution is to set the two env. variables to : TTRSS_SELF_URL = http://host_ip:port/ and SELF_URL_PATH = http://host_ip:port/ |
Note: there's also an issue with TTRSS_PORT that you could also solve. It get's a double colon in lines 81 and 97. |
A quick note is that it seems like the request url must match exactly how the SELF_URL_PATH is set up. |
I just wanted to throw in my 2 cents into this problem. How did you workaround this problem? |
try to add these ENVs:
its working for me this way |
Thank you very much @thiesschneider |
Looks like this is solved -- can we close this? Thanks for the help, @thiesschneider. |
Please adjust documentation before closing?
…On Wed, Nov 8, 2017 at 6:23 PM, x86dev ***@***.***> wrote:
Looks like this is solved -- can we close this? Thanks for the help,
@thiesschneider <https://github.com/thiesschneider>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABzd_LBsGekI4w0KMc_Kt1LJ3QEbNRPlks5s0jfegaJpZM4OYRqm>
.
|
Hi, its working for me this way. This is an example. SSL:
URL to open: https://192.168.1.124/ Non SSL:
URL to open: http://192.168.1.124:8080/ |
Hi,
Thank you for this nice docker image.
I use it with the letsencrypt nginx proxy.
With the default configuration I cannot access the web page and I get an error with incorrect SELF_URL_PATH.
I tried to set SELF_URL_PATH as an environment variable but it is not used.
I did workaround by passing these environment variables:
Setting the TTRSS_PORT as 443 does not work, I had to omit the value (even if it is 443).
I don't know if it is a bug but it should be at least documented to avoid debugging ...
Thanks.
The text was updated successfully, but these errors were encountered: