What its wrong ? all websites without database working great ... but when i need https://ip/phpmyadmin its error 404 not found nginx/1.4.6 (Ubuntu) Solutions please ?
lol Yeah i love this genial answers Logical .... https://ip:8080/phpmyadmin ... or https://ip:8081/phpmyadmin probably soon another great answers : delete your cockie , try another browser ... bla bla
another server On another server , give me the same error but before appears this : ssl_error_rx_record_too_long
Have you read your own first post? You posted there that you tried to access phpmyadmin on port 80 on a nginx server. Have you read the perfect server guides for nginx? There you can read that phpmyadmin is on port 8081 on all ispconfig nginx servers. If you would have even read my post above at all, then you would know why you get the error: I told you to use: http://ip:8081/phpmyadmin but you used: https://ip:8081/phpmyadmin You know that http and https are different communication protocls abd that you cant access a server socket listening on http not with https
great My ISPconfig its working , phpmyadmin its working but ... i have one question Who use wordpress , have some error if on settings/permalinks change the option Default with Post Name or anything => show me the error 404 nginx Thanks
Did you add the nginx directives to allow nice URL Rewriting in wordpress? You have choosen nginx as your webserver and not apache, nginx is a new and fast webserver, but inlike apache, cms systems will not work out of the box on nginx as nginx does not understand the rewrite rules in the .htaccess files of the cms systems. On a nginx server, you have to translate the apache rules to nginx syntax and then add them in the nginx directives field on the options tab of the website in ispconfig. So a nginx server is not recommended for beginners, it is a system for advanced system administrators. For common cms systems like wordpress, there are translated rules available on the net. For wordpress you can use: Code: location / { try_files $uri $uri/ /index.php?$args; } # Add trailing slash to */wp-admin requests. rewrite /wp-admin$ $scheme://$host$uri/ permanent; location ~* \.(jpg|jpeg|png|gif|css|js|ico)$ { expires max; log_not_found off; }
i just tell u , in my case all its working ... but just if i change that option ... i see that error ... and for fix it ... i need to be expert ? So my wordpress its working good , just if i choise option permalink non default . then appears error 404 ! Then what u say ... to reinstall ispconfig and choise apache just because i see that "simple" error ... and im very sure can be fixed just with copy/paste in one file ...
I expained you why you see that error and how to fix that, its a simple copy/paste job and not even a file has to be edited. And where did I tell you to reinstall ispconfig? The word reinstall is nowhere in my post.
location / { try_files $uri $uri/ /index.php?$args; } # Add trailing slash to */wp-admin requests. rewrite /wp-admin$ $scheme://$host$uri/ permanent; location ~* \.(jpg|jpeg|png|gif|css|js|ico)$ { expires max; log_not_found off; } So i put in what file exacly this ?
Thanks for your answer ! I dont understand nothing ! So i must to edit , add something ... where ? I login in ISP after there its something Directives ... i dont find nothing like that! Maybe Directive Snippets ? or its about the file /etc/nginx/sites-available/ file default ?
Login to ispconfig. open the list of websites, click on the website to edit it, go to the options tab and there add the lines in the nginx directives field.
I hate to bring up an old thread but if all of my sites are going to be wordpress is there a setting somewhere I can add so that this is server wide or do I have to add this to every single one of my sites?
till I mean this part: Code: location / { try_files $uri $uri/ /index.php?$args; } # Add trailing slash to */wp-admin requests. rewrite /wp-admin$ $scheme://$host$uri/ permanent; location ~* \.(jpg|jpeg|png|gif|css|js|ico)$ { expires max; log_not_found off; } Is there a server wide way of doing it or do i have to add those directives on a site per site basis?
