Today I wanted to add an email account to my seafile pro (v6.0.4) instance so I do not have to copy/paste share links to emails.
I added my email account information to seahub_settings.py, deleted seahub_settings.pyc (just to make sure the information is really updated) and restarted seafile and seahub.
If I try to send a link now, first seahub displays “sending” for a few seconds, then a “Internal server error”-Message is displayed in the modal.
Looking up the Console in Chrome, I found that a 400 error is issued (Bad Request) for the resource: https://my.seafile.domain/share/link/send/
This is also found in seahub_django_request.log:
2016-12-19 15:40:41,573 [WARNING] django.request:170 get_response Not Found: /share/link/send/
My seahub_settings.py (E-Mail part only):
EMAIL_USE_TLS = True
EMAIL_HOST = 'smtp.my.domain'
EMAIL_HOST_USER = 'my@email.address'
EMAIL_HOST_PASSWORD = 'myCorrectPassword'
EMAIL_PORT = 465
DEFAULT_FROM_EMAIL = EMAIL_HOST_USER
SERVER_EMAIL = EMAIL_HOST_USER
My nginx config: (without ssl-config etc.)
location / {
fastcgi_pass 127.0.0.1:8000;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param PATH_INFO $fastcgi_script_name;
fastcgi_param SERVER_PROTOCOL $server_protocol;
fastcgi_param QUERY_STRING $query_string;
fastcgi_param REQUEST_METHOD $request_method;
fastcgi_param CONTENT_TYPE $content_type;
fastcgi_param CONTENT_LENGTH $content_length;
fastcgi_param SERVER_ADDR $server_addr;
fastcgi_param SERVER_PORT $server_port;
fastcgi_param SERVER_NAME $server_name;
fastcgi_param REMOTE_ADDR $remote_addr;
fastcgi_param HTTPS on;
fastcgi_param HTTP_SCHEME https;
access_log /var/log/nginx/seahub.access.log;
error_log /var/log/nginx/seahub.error.log;
}
location /seafhttp {
rewrite ^/seafhttp(.*)$ $1 break;
proxy_pass http://127.0.0.1:8082;
client_max_body_size 0;
proxy_connect_timeout 36000s;
proxy_read_timeout 36000s;
}
location /media {
rewrite ^/media(.*)$ /media$1 break;
root /home/seafile/seafile-server-latest/seahub;
}
Unfortunately, there is NOTHING related to email in any of the log files.
I’m pretty sure that this is a routing error…
Any ideas, where to search next?
best
Oliver
