I have just installed wamp and I copied all the projects inside www folder but when I browse http://localhost/project its displays error like this.
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster#localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
I also changed the php setting and extensions but not working. So can anyone suggest for me.
Thanks
There can be a large number of possibilities for this error. for now, check to see if your project is using any php module that is not registered in php.ini. also check ur php.ini and httpd.conf (or whatever your apache config file is) )to see if all modules are configured correctly
I made it working. As I am using htaccss and I forgot to enable rewrite_module so it did not work. Now it works perfectly. Thanks to all of you for your answers that made me find out the solution. :)
Related
I got one err: Error 405 -Method Not Allowed,
so, I want to enable SSO for IS,
then I modified <IS_HOME>/repository/conf/security/authenticators.xml.
but, after I restarted IS server, authenticators.xml be recovered to original value.
Finally, Error 405 still be showed.
Can you tell me how to enable SSO for IS?
Thanks much!
henry
If you have built the source code of the master branch, then it is 5.12.0-alpha10-SNAPSHOT If you download the zip here https://github.com/wso2/product-is/releases/tag/v5.11.0 it's IS-5.11.0
IS 5.9.0 onwards all configuration changes of XML files are maintained via a central location (deployment.toml). Therefore, in order to make your change navigate to <IS-HOME>/repository/conf/deployment.toml and add the following config. Then restart the server and check the relevant XML file. It should be changed.
[admin_console.authenticator.saml_sso_authenticator]
enable=true
Find more info about deployment.toml configuration model : https://www.youtube.com/watch?v=BRWvtcV1T94
At the recent time, I was trying to setup an SFTP on my AWS lightsail - Ubuntu Plesk instance. Once I noticed my current user doesn't have access to vhosts/example.com/httpdocs folder, I tried to give the current user access rights with giving this command on ssh :
- sudo chown -R (my-username)
after that I sucessfully got the access to desired folder on my sftp client.
But unfortunately, there was something wrong on its domain when I accessed in browser with 503 Error. And also the file manager in Plesk returned an Error 13.
after recover the the user permission with this command :
- /usr/local/psa/bin/repair --restore-vhosts-permissions
the file manager was back to normal, but not the website domain : which still has 503 error.
any idea what's wrong with that? I believe this has to be user permission problem, but couldn't find anywhere else to fix it. not to mention, I am newbie on Ubuntu server.
hope to find some decent answer here :) Thanks and have a good day!
So, After few months of deploying VPS in AWS Lightsail with Plesk, There are few things that could lead this problem happen.
1. Permission is not enough for the directory, make sure you have at least 755 for the root or desired directory you want to access.
2. The PHP version and Nginx/Apache Configuration can also be the issue. In some cases, The current Plesk Onyx delivered along with Nginx and Apache, I always choose "FastCGI application served by Apache" and it is often solve the problem. This setting can be found "websites & Domains > PHP Settings"
3. Missing Index.php or Index.html or reference file for indexing. So the server is confused to interpret which file should be access first.
I hope this solve someone else problem. Discussion can be continued on the comment. :) Have a good day!
Blackfire gives me "Are you authorized to profile this page? Probe not found or invalid signature." on my WAMP install!
I followed all the steps correctly and installed everything in the right places.
Things to keep in mind while setting up Blackfire on WAMP:
Make sure Xdebug and other debugging extensions are disabled in the php.ini file.
Client ID and Client Key are different from Server ID and Server Key - see that you are not pasting them in the wrong places.
Set up a log directory to make sure you get to know about errors. Example: blackfire.log_file = /path/to/logs/blackfire.log
Make sure the blackfire-agent.exe is running while you try to profile the site running on your localhost - this is what I was missing. You can run it with the command blackfire-agent in the command prompt.
Hope it helps! Happy coding!
I just installed ColdFusion 11 on a Windows 2008 server. After installation, I got the message to proceed with configuration using the link
http://foo.com:80/CFIDE/administrator/index.cfm
where foo.com is 127.0.0.1
However, it keeps rejecting the userid and password I provided during installation for administrator.
Any help is highly appreciated.
This blog entry should help you: Troubleshooting ColdFusion Admin Login Issues.
You can also try the following quick workarounds:
Try an alternate browser (issue primarily occurs with IE).
Try alternative address
http://127.0.0.1:port_no/CFIDE/administrator/index.cfm or
http://localhost:port_no/CFIDE/administrator/index.cfm or
http://ip:port_no/CFIDE/administrator/index.cfm.
Try the passwordreset.bat and then try with the same ip or loopbak ip
address.
Enable internal/built port for ColdFusion and then try
http://localhost:8500/CFIDE/administrator/index.cfm, where 8500 is
the internal port for ColdFusion.
Note: Enabling internal/built port would require a ColdFusion Application Server restart.
This is usually due to reasons posted here - https://forums.adobe.com/message/6502639#6502639
The issue is happening because of mime type (.air) entry specified in the web.config of the webroot.
Can you try the following steps:-
Navigate to the webroot of your site.
Take a backup of web.config and open it with text editor (notepad etc)
Comment the entry for mimeType extension of ".air" like <!--<mimeMap fileExtension=".air"
mimeType="application/vnd.adobe.air-application-installer-package+zip"
/>-->
Save the file and restart IIS.
Launch CF Admin and try to login.
Commenting out the .air type in site specific web.config file has resolved the issue.
I've pulled the latest stable MOODLE_21_STABLE branch to my WAMP server localhost location, all installed and configured successfully, works in browsers as per usual. I'm poking around theming now, and would like to test out device-specific themes.
SO questions helped me successfully connect to my localhost via iPhone Safari and Android Chrome, I can navigate the various projects and tools I have on localhost - all of that works wonderfully (successful URL eg: http://192.168.123.135/ - this is the root WAMP page).
Next, I tried to access my Moodle install via Safari (URL for reference: http://192.168.123.135/moodle/moodle2/htdocs/), but Safari prompts an error:
"Cannot Open Page. Safari cannot open the page because it could not connect to the server."
The page beneath the prompt reads:
"Incorrect access detected, this server may be accessed only through 'http://localhost/moodle/moodle212/htdocs' address, sorry. Please notify server administrator."
Two things to note:
Safari re-writes the IP address portion of the URL to 'localhost' for the failed Moodle URLs I've been trying to enter, when it prompts the error. My own project URLs keep their IP portion.
The above 'suggested' address in the page error also delivers the same error message again.
I feel like I'm inches away from awesomeness here, does anyone have any advice/ideas as to how I can access my Moodle install on a WAMP localhost (or similar), when browsing via device?
Is there some server setting I need to dis/enable?
Is this likely to be a Moodle specific issue, or is there something about accessing server locations in this way that is troublesome/not possible?
Make sure that both $CFG->wwwroot and the IP address of the Apache vhost in the WAMP configuration files are set to 192.168.123.135. Also possibly the hostname too. It sounds like you have a config issue with internal and external DNS names not resolving in quite the same way. Apache is probably the culprit.
Are you referring to desktop Safari installed on the same machine as WAMP?