I recently downloaded CommandBox to try to set up a Lucee Server. I have a folder called LuceeSever with an Index.cfm page. When I type the command "box server start" it opens a window at this address: http://127.0.0.1:54613 displaying my index.cfm page. Cool.
But I would like to connect a datasource and I would like to do this thorough the server admin panel that everyone else says to use. So when I try to access http://127.0.0.1:54613/lucee/admin/server.cfm I get this screen:
So I created a password.txt file that contains 1 line of plaintext that is the password I wanted to use. So my directory looks like this:
LuceeServer>
index.cfm
password.txt
In which index.cfm and password.txt are at the same level. When I click import file the screen reloads and nothing happens.
I assume I have things set up incorrectly. I've never used commandbox before and I dont really know what I'm doing.
You can bypass this entirely by using CFConfig. You can either specify the adminPassword in your .cfconfig.json file
{
"adminPassword":"myPass"
}
or you can install commandbox-dotenv and set a global .env file that has a cfconfig_adminPassword key.
~/.box.env
# Add environment variables to be loaded into CommandBox when it starts
# Variables are in the form of foo=bar, one per line
cfconfig_adminPassword=myPass
Disclaimer: I am the lead developer of CommandBox and the CFConfig module.
When you run your server with CommandBox, click on its tray icon in the right corner of your desktop, click open and then the server home folder like shown on the image below:
Then navigate to /WEB-INF/lucee-server/context/ and place your password.txt file there. Then go back to lucees server admin page in your browser and click the "import file" button to import the password.txt file.
Your password.txt needs to go in the "root Lucee server directory", which isn't the same as your site's web root (which wouldn't be a very secure place to put it). In CommandBox the location is a bit obscure, but you can find it with the following command:
server info property=serverHomeDirectory
Related
I have hosted the jorani Open Source LMS, under local server and after logging in, redirects me to home page (http://localhost/lms/home), but I get a 404 - File or directory not found. error.
What can I do to fix this? I know I need a server configuration but I don't know what. Thanks
It seems that you didn't activate the rewrite module.
Jorani contains a page at the root of the installation (e.g. http://localhost/lms/requirements.php) that checks your system and tell you what is missing.
You should read the manual of installation.
EasyPHPs homepage is accessed from : http://127.0.0.1/home/.
Virtual Host manager sets a local domain name to redirect to 127.0.0.1 in the hosts file.
When I navigate to 'mylocaldomain.com/home/' I get an error 'The requested URL was not found on this server.' because '/home/index.php' is used for the Admin Panel of EasyPHP.
I need to use '/home/' in my local domains, so I want to try and change the default URL that EasyPHP homepage is using.
Any ideas?
I just had this problem and ran across your question. This is how you solve it:
Access your EasyPHP Apache config file (on Windows, I right-click on the taskbar icon, go to Configuration, then click Apache)
Look for the line Alias /home "${path}/binaries/home" - Mine was at line 359
Change the first /home to /something-you-won't-think-to-use-on-your-websites
Restart the server
That should do it
I want to move *.out log file of Node manager to my own custom location.
Thanks in advance.
Passing following arguments on Weblogic console, I was able to change the default location of *.out nodemanager log file.
-Dweblogic.Stderr=/usr/local/Weblogic12c/logs/error/servererror.out
Add the options -Dweblogic.Stdout=<outfile> and -Dweblogic.Stderr=<errorfile> In order to move all logs to a separate location.
In addition to changing the location of the file, you can also redirect more of the output to the standard .log file defined for the server.
Something similar to the command line options -Dweblogic.Stdout=<outfile> and -Dweblogic.Stderr=<errorfile> is to login to the weblogic console and do the following for each server:
Servers -> <server name> -> Logging Tab advanced section ->
Check both "Redirect stdout logging enabled" and "Redirect stderr logging enabled"
Unfortunately this does not help with the fact that the .out files will grow in size without being rotated. See this link for some info on how you can rotate the .out files yourself.
I was try to upload a file using the Drop box Saver as following:
"https://www.dropbox.com/developers/dropins/saver"
I see the Drop box saver button and when I'm clicking on it I get an error: {"error": "Invalid origin"} in a popup...
I also added to the "Drop-ins domains the local host ip,127.0.0.1
In the popup window that open when clicking on the button there is the uri:
https://www.dropbox.com/saver?origin=file%3A%2F%2F&app_key=undefined&version=2
Maybe the problem is that after the word "file" there are the following characters %3A%2F%2F and there is no file name or location...
app_key is undefine although i added it
What can i do?
It looks like you're opening your HTML directly from the file system instead of running a web server. I believe you'll need to actually run a web server (could be as simple as python -m SimpleHTTPServer) so the URL in the address bar starts with http (or https) and has a domain.
I have setup TYPO3 successfully on my local server. But I am having problem when clicking on any menu item: It's showing "url not found on server".
When I type in the URL manually into the browser it shows the page. It's only having problems when redirecting after clicking on a page item at any frontend website page.
That might be related to the domain config or RealURL... or both ;)
Do you use RealURL? Or do you use the standard url config?
If links to sub pages look like index.php?id=12345 you are using the standard config.
My guess is that the local DNS ("hosts file") is not configured correctly.
With the hosts file you can simulate how the web site will appear when it's online, hooked up to a "real/global" DNS. (Not quite, but in a nutshell)
So if you set up Typo3 to be reached under http://www.example.com/ you need to tell your local DNS ("hosts file") to route a request to http://www.example.com/ to your local host e.g. http://127.0.0.1/ . In that case your host file needs an entry like so:
127.0.0.1 http://www.example.com/
What Domain do you enter to reach your web site? Where do the links from the menu link to?
If you wanna know mor about the "hosts file" look here:
http://accs-net.com/hosts/how_to_use_hosts.html
If you can log in into the TYPO3 backend (/typo3/) and can access the frondend through /index.php, but not through the generated menu links, then RewriteRules for mod_rewrite don't apply.
Usually TYPO3's installer should detect this configuration and disable RealURL, which is responsible for generating such nice looking URLs (instead of index.php?id=123). It seems like this failed (or you copied everything afterwards without the .htaccess file?).
Make sure that you have TYPO3's .htaccess file in place in the root directory of your installation. If this is the case, make sure that mod_rewrite is enabled in your Apache config.