![]() I am back in the same boat as before in my previous post. I remoted in to own cloud with Quixplorer to look at the config.php file and all of the amendments I had made to trusted domains etc were gone along with my changes to file size limits in the light (something) file too. I shut down the own cloud app and the share centre has been fine running for a couple of days no stability issues. The only way to get it responsive was to pull the power plug as holding down the power button did nothing. I could type in my dlinkddns and local IP and the sharecenter login page would start to load but would never finish. The fan was going / all lights on the front and the network lights round the back were flashing like mad. The eventually was causing my DNS to crash. Until I added a second hard drive the other weekend and used the prompt to configure it to RAID 1 without erasing the existing Data.ĭuring the following week my own cloud install had been using 99% CPU resources and the same RAM. I reset the DNS-327L and reinstalled everything and since then own cloud has been working like a dream. who would have thought a little power cut would cause this much trouble. I am thinking I am a lost cause and going to admit defeat and that I should nuke my DNS-327L and do a hard reset to flush out all the settings etc and restart from scratch, unless some-one can give me some advice to the contrary?Īs always I look forward to your help and suggestions, you've all been so helpful up until now. I had read a previous response to the "internal server error" being to do with the SQL so I tried to run the fix they suggest but whenever I try to log in with myPHPadmin I get "#2002 Cannot log in to the MySQL server" error.ĮDIT: I have tried every combination of what is the standard admin/admin root/admin etc etc and all the possible combinations I might have inadvertently changed it to and I still get "#2002 Cannot log in to the MySQL server" error and my own cloud gives me "Parse error: syntax error, unexpected '\' (T_NS_SEPARATOR), expecting identifier (T_STRING) in /mnt/HD/HD_a2/Nas_Prog/owncloud/owncloud/config/config.php on line 3" from a fresh own cloud install. ![]() Re-install own cloud click on Launch interface and I get the "Parse error" still. So unistalled the add-on restarted the NAS, went in with QuiXplorer and Owncloud folder isn't there so the config.php is gone. I wondered if it was getting left behind. On a new install, I haven't even touched the config.php. ![]() So I uninstalled Owncloud and restarted my DNS-327L and re-installed the own cloud add-on. However I didn't amend anything in line 3 of the config/php. "Parse error: syntax error, unexpected '\' (T_NS_SEPARATOR), expecting identifier (T_STRING) in /mnt/HD/HD_a2/Nas_Prog/owncloud/owncloud/config/config.php on line 3" My trusted domains had vanished from my config file so I used QuiXplorer to add them in like I did initially and now whenever I try to log in, from my local IP and drink.ddns address it gives me an error Perhaps foolishly I had a look at the log and my config file. More details can be found in the server log." Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. The server encountered an internal error and was unable to complete your request. Now I cannot log onto my own cloud instance. After successfully getting OwnCloud up and running and enjoying seamless syncing from my server, pc, mobile, laptop and iPad I have a power cut at home over the weekend.
0 Comments
Leave a Reply. |