Stu

Hi Stu,
Google and others can be convenient but if you really care about your data you might want to self-host this.
If you're not keen on that, you can meet in the middle and go with a mail provider that is smaller and more focused on the security and integrity of your data.
Cheers

Hey Stu,  you may get more interaction on this if you post in our discord server https://discord.gg/UNs26C.  If you feel like being an especially nice person you could even post back on here some of the answers you get

I'm happy to be able to say, this is actually the main focus of v4.11.0  https://dev.blesta.com/browse/CORE-3356
 

What he said ⬇️
 

@Stu Cyandark (https://clients.cyandark.com/)
They are absolutely fantastic!

To follow up on this, I've set nginx to pass everything to apache and it now works.
So this is clearly nginx caching causing the behaviour.
 
Thanks

To follow up on this, I've set nginx to pass everything to apache and it now works.
So this is clearly nginx caching causing the behaviour.
 
Thanks

Very useful addon and well coded.
I wouldn't be without it.

Just got a bug patch soon when @cyandark spots it on github haha  but only effects addon companies / multi-language.

Very useful addon and well coded.
I wouldn't be without it.

Messed with this for a while after posting the question.
I have come up with the following which seems to work....
 
location / { try_files $uri $uri/ /index.php?$args; } location ~ \.php$ { try_files $uri =404; fastcgi_split_path_info ^(.+\.php)(/.+)$; fastcgi_connect_timeout 60; fastcgi_send_timeout 180; fastcgi_read_timeout 180; fastcgi_buffer_size 128k; fastcgi_buffers 4 256k; # fastcgi_busy_buffers_size 256k; fastcgi_temp_file_write_size 256k; fastcgi_intercept_errors on; fastcgi_pass 127.0.0.1:9000; fastcgi_index index.php; include fastcgi_params; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; } # Deny all attempts to access hidden files # such as .htaccess, .htpasswd, .DS_Store (Mac). location ~ /\. { deny all; } # Disallow access to any file with .pdt extension location ~ (\.pdt) { return 403; } }  
If anyone wants to add to this please feel free to post.

Reissued the blesta_cms license and everything is fine again.
Thanks for your help @cyandark and @Licensecart

Reissued the blesta_cms license and everything is fine again.
Thanks for your help @cyandark and @Licensecart

Reissued the blesta_cms license and everything is fine again.
Thanks for your help @cyandark and @Licensecart

Stuart mate do you have a IPv6? feel free to pm me or live chat so we can add it to the license.

This message is not from Blesta, It's from BlestaCMS. Try to re-issue your BlestaCMS License.
@Licensecart can help you.

oh oops forgot I had installed that, I thought I was still working on a clean blesta install lol.
 
My bad, thanks guys

Hi Guys,
 
can some people show me their nginx configs for blesta?
I had it working using the 'try_files $uri' way of doing things, but I reinatlled my server and forgot how I made it work before.
I am currently using a method i found on here elsewhere (thanks to that poster),
but I would like to get back to the 'try_files $uri' method as it was much cleaner and simpler.
 
Here is what i'm currently using...
location / { error_page 404 = @blesta; #IF file doesn't exist log_not_found off; } location ~ \.php$ { try_files $uri =404; fastcgi_split_path_info ^(.+\.php)(/.+)$; fastcgi_connect_timeout 60; fastcgi_send_timeout 180; fastcgi_read_timeout 180; fastcgi_buffer_size 128k; fastcgi_buffers 4 256k; # fastcgi_busy_buffers_size 256k; fastcgi_temp_file_write_size 256k; fastcgi_intercept_errors on; fastcgi_pass 127.0.0.1:9000; fastcgi_index index.php; include fastcgi_params; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; } # Disallow access to any file with .pdt extension location ~ (\.pdt) { return 403; } if (!-e $request_filename){ rewrite ^(.*)$ /index.php; } #Core rewrite location @blesta { rewrite ^(.*)$/index.php/(.*) /$1 permanent; } }  
I remember before I was using something a lot simpler, something like...
 location / {
               try_files $uri $uri/ 
               then the fastcgi_pass stuff

Well I couldn't figure this out, and the VPS was behaving a little strange in general so I deleted the server and created a totally new droplet.
I completed the installation exactly as I had done before and now everything is fine and working great.
Its perfectly possible that I missed something the first time round, I really dont think I did, but its possible.
Anyway, all working now
Thanks for your help guys

Thanks for the tips guys.
I did indeed upgrade to a 1GB droplet.

Well I couldn't figure this out, and the VPS was behaving a little strange in general so I deleted the server and created a totally new droplet.
I completed the installation exactly as I had done before and now everything is fine and working great.
Its perfectly possible that I missed something the first time round, I really dont think I did, but its possible.
Anyway, all working now
Thanks for your help guys

Try upgrading your droplet to 1 GB

For testing and maybe even production, depending on how many customers you have, a 512Mb instance is probably more than enough.  You may need to tune some things to work better under a lower ram environment, such as mysql, or you can supplement it by adding swap which will probably rarely get used.  An example for centos 6 is something like this https://www.digitalocean.com/community/tutorials/how-to-add-swap-on-centos-6

Morning,
 
It looks like your CSS and images are not loading. Maybe a permissions issues or you forgot to upload the files / folder.
View the source on the webpage, and try to load a CSS file. See what the server response back with:
Example:
Visit: domain.tld/app/views/client/bootstrap/css/bootstrap.min.css
-Adam
 

looks like I ran out of memory on my low budget test server and mariadb crashed.
Restarted it and everything is fine.
How much memory do you recommend for a live production blesta install?