Stu

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

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.

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

Posting this for others...
Thanks for your help Paul
 
 
Creating a package and selecting the SolusVM module should prompt an API call to your SolusVM master server.
For SolusVM, when managing the module under Settings > Company > Modules, you should create a Server Group and add your SolusVM master server into the group. The reason for this is that there's a bug with 4.0 that will not populate the module fields correctly if it doesn't belong to a group.
In either case though, you should see the API request in Tools > Logs > Module log. Click the row to expand. It should look something like this:
INPUT
your.solusvm.server|list-plans
a:1:{s:4:"type";s:3:"xen";}
OUTPUT
your.solusvm.server
<?xml version='1.0'?>
<status>success</status>
<statusmsg></statusmsg>
<plans>
<plan>
<id>9</id>
<name>20</name>
<ipv6subnets>0</ipv6subnets>
<automatedbackups>1</automatedbackups>