-
Notifications
You must be signed in to change notification settings - Fork 1
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
Conversation (+attachments) not working: NGINX problem ($query_string missing / Redirect loop?: https?) #8
Comments
Hi @mo-kuh, I can confirm that the above solution is working, for the conversation and for the attachments. Thanks a lot for the workaround and great work. |
However, just noticed that I have another issue now. I get the 'Whoops, looks like something went wrong.' page. Troubleshooting was as described issue-31, but it is not sustainable. The page comes back again after everything working properly.
The problem is solved every time after I run the Any ideas what might be or does anyone else is having the same issue? |
There was another issue with permissions on /var/www/freescout/storage/, I fixed it with |
@mo-kuh thank you very much, you gave me the necessary bits to fix a loop that killed conversations for me. what I used was;
reloading nginx and it works like a charm. I'm very happy to have Freescout in yunohost, looking forward to it's future development and further integration (LDAP users and so on). |
Just a small info: Updating FreeScout via YUNOHOST did break it again. I tried to fix it but couldn't do it quickly. Menu (clicking on it didnt do anything) + Conversation (404 again: "/var/www/freescout/public/index.phpfolder_id=1" failed (2: No such file or directory)") where not working :( Workaround:
Whenever there is time i will try to make a fresh install of FreeScout and see its still broken out of the box. |
Hi, this is happening again after updating. Is there a plan to fix it for once? |
No more working I always get the following error: <404 Not Found>. the only solution is the following comment |
I wanted to simplify the steps for fixing the too many redirects issue as it took me a bit to figure out what exactly the above folks had done. In /etc/nginx/conf.d/yourdomain.com.d/freescout.conf
In /var/www/freescout/.env
For reference, my freescout.conf looks like this now that it is fixed:
|
will you be able to provide the permissions applied to Edit. Is this with the update from testing branch? |
I have not been able to get the testing branch to install as of yet.
also running |
Hey, thanks you so much for making freescout available for yunohost (of which I am a great fan of 💯)! Sorry if my message is akwards, i pst anything on github before ...
Unfortunately i spent 2 days to find bugs in the yunohost app. Most is working, so I want to share the solutions. I hope it helps others who benefit from you bringing freescout to yunohost 🥇
My setup:
MxLinux = Debian 11 (update to date)
Yunohost 11.2.8.2 (up to date)
Freescout : 1.8.113 (original app installed version) + 1.8.115 (updated via freescout web console)
Browsers: Firefox 121 (+ Chromium = for testing)
My problems:
1) Problem in NGINX config ("freescout.conf")
I dont know why, but the nginx config of the yunohost app differs from the "standard" nginx config as stated in the freescout install guide.
1.1) Wrong nginx location path (root)?
The nginx access logs for my domain recorded alot of errors ("No such file or directory") involving "/polycast/..."
On my server there is no "/usr/share/nginx/htmlindex.php" (or "/usr/share/nginx/html/..."). Nothing that freescout was looking for existed under this path. The correct path root is "/var/www/html/public".
I think i solved this problem by using the code from the freescout install guide:
Change
alias /var/www/html/public;
to
root /var/www/html/public;
As I understood it: in some situations nginx couldnt find any matching location in the freescout.conf and did fall back to higher locations with their corresponding roots. In the end the last fallback is the default root ("/usr/share/nginx"). The default root can be changed, but I dont know if this is helpful if you are running other software. You can find a bit more info on this (nginx root) topic here: https://serverfault.com/questions/920880/nginx-defaults-to-usr-share-nginx-html
1.2) Conversation = "Too many redirects"
Most of freescout worked out of the box but I couldnt do anything with "conversations", besides creating new emails. Meaning: I couldnt click on emails titles to see their content or reply to them. Everything the went to "/conversation/..." did end in firefox and chrome aborting the request after some time (1+ minute) or some tries (around 20) with the statement: "The page isn’t redirecting properly" (Firefox) or "ERR_TOO_MANY_REDIRECTS" (Chromium). You can read more about this behaviour here: https://blog.hubspot.com/website/too-many-redirects.
My nginx access logs recorded alot of HTTP "302" errors:
Its often assumed that this is due to https (certificate) problems and thats why I had alot of trial and error trying to force freescout to use HTTPs:
In the end i added the following code to 3 of my files (A+B+C):
A) freescout environment variables file (".env" as I found it in /var/www/freescout/.env"):
After changing the ".env" file you have to reload freescout. You can do this fro the webconsole (Manage/System/Tools/"Clear Cache" Button) or command line:
/bin/php8.2 /var/www/freescout/artisan freescout:clear-cache
I cant tell if any of this helped :(
B) freescout.conf (as found in /etc/nginx/conf.d/freescoutsubdomain.domain.end.d/freescout.conf)
I added "fastcgi_param HTTPS on;" in the location block dealing with ".php" files:
C) If you are using nginx as a reverse proxy, then some said that the following code is helpful:
I added this to the nginx configuration of the domain where freescout is running on ( /etc/nginx/conf.d/freescoutsubdomain.domain.end.conf)
Nothing worked. I almost gave up and was looking at the nginx conf from the freescout install guide "one last time" :)
D) I saw a difference to my servers nginx conf and thought: i did try to change this at the beginning but it didnt work back then. I tried it again, and the conversations where working!
nginx conf from Freescout install guide:
IMPORTANT: You have had to add "$query_string;" to 2 locations:
NOTE: There are more difference in the nginx configurations used by the yunohost app and the freescout install guide.
2) Conversation attachments not working :(
While writing this I found out that email attachments produce HTTP error "404 Not Found" :(
I guess it has something to do with this part of the nginx freescout.conf:
I hope i get it fixed.
The text was updated successfully, but these errors were encountered: