I am following the documentation here http://designers.hubspot.com/docs/tools/local-hubl-server but when running the local-hubl-server Batch file (after unzipping the package), the browser opens a username/password window. What are the credentials? I tried root/root, admin/admin and blank username and password. I also checked the config.yaml file but I couldn't see any parameter to set the username and password. I am running on Windows 7 and JDK 1.8.0_144
Issue was another service was running in the same port as the HubL server was supposed to run. Edited the port in the config.yaml file and no username/password prompt appeared anymore.
Related
I'm currently trying to connect my intellij installation to a remote websphere server (version 8.5.5.14). When I start making the configuration it gives me a message "Username but no password specified". The thing is, there's no password input in the form. So how do I specify the password?
In the recent versions, IDEA ensures that the plain passwords are never stored in the project- or application- level configuration files. All the passwords previously stored in the application servers run configurations should be automatically moved to KeePass manager or Mac Keychain after an opening of the project.
We also decided to not allow to specify passwords in the template run configurations, so your screenshot is as expected.
There was a bug preventing the passwords fields from showing up in the normal non- template run configurations, but it should be fixed in the final builds for 2018.3.6 and 2019.1 streams
I am behind in my company's firewall. We use a certificate file *.crt provided from our company to access SSL enabled web sites.
So I am getting unable to get local issuer certificate error when using heroku login.
I am using Windows 10 and Heroku CLI 7.14.1 and tried adding HEROKU_SSL_VERIFY=disable and SSL_CERT_FILE=C:\certificate.crt as environment variable but no success.
How can I solve that?
Solved from https://devcenter.heroku.com/articles/using-the-cli
Add an environment variable as NODE_EXTRA_CA_CERTS that points to the certificate.
For Windows:
set NODE_EXTRA_CA_CERTS=C:\path\to\ca_cert.pem or .crt
For Linux:
export NODE_EXTRA_CA_CERTS=/path/to/ca_cert.pem
For Windows 10:
Go to System variable (Windows logo key > type: "environment variables" > click Environment Variables button)
Check/Set Variable SSL_CERT_DIR=YourCetrFolder
Certificate folder Example:
Ask your organization network team to provide the ca cert or pem file. Once you have the cer or .pem file in your local computer, place it in some directory and set it in environment variable.
For example: I have .pem file placed in this location. 'C:\keys\xxx.pem'.
In environment variable i will add new system variable with below given name and value.
Variable Name: 'NODE_EXTRA_CA_CERTS'
Variable Value: 'C:\keys\xxx.pem'
Once the above steps are followed, open command prompt (close if you have one already opened) and try to enter 'heroku login' and press any key on your keyboard to take you to browser. It will take you to browser to authenticate your user credentials. If your organization has SSO enabled it will take care of itself if not you have to enter your heroku user credentials to authenticate. Once successfully authenticated, you will get back to command prompt with below messages.
Opening browser to 'https://cli-auth.heroku.com/auth/cli/browser/XXXXXXXX'
Logging in... done
Logged in as 'your user name appear here'
That's it.
I have a Raspberry Pi set up as a download server at home. To access it from any Windows PC I download Putty and add its parent folder to the Path environment variable.
When accessing it via SSH using Putty GUI or CLI from any PC on my home network, it attempts to login with an SSH key, if it fails it prompts me for a password, and I can login.
I set up an ngrok account to be able to access the server from work (ngrok uses the same address for all users, but each free user gets a specific port, randomized on server reboot).
If i open up Putty's GUI and add the address (0.tcp.ngrok.io) and my port (13495) and click Open, I login normally, SSH key first, if that fails, password prompt, and I can login; as shown in the following picture: Putty GUI Login
However, if I login by command using "putty root#0.tcp.ngrok.io:13495" from the command line or making a Windows shortcut with that command as the target, it reacts as if password authentication is disabled and the only authentication method is via SSH key, which is not the case. (Failed Putty Logins)
I finally attempted to add the SSH key of my work desktop to the authorized_keys file, nothing changed. I can login by GUI using the key, but CLI login still fails.
I have tried resetting all of Putty's settings, redownloading, using Pageant instead of the Putty settings SSH>Auth, nothing works.
I have searched far and wide and delved into the creepy depths of the Internet and cannot find ANYONE with the same problem. If someone does find a post with the same question, well then that post must be running away from me.
Help me, please.
This is starting to get quite irritating.
Thanks in advance.
It's because PuTTY actually ignores everything after the colon (for a consistency with PuTTY psftp and pscp tools, where you specify a path after the colon).
So the putty root#0.tcp.ngrok.io:13495 works like putty root#0.tcp.ngrok.io. That means you actually connect to the default SSH 22 port, not to the 13495.
You have to use the -P switch to specify the non-default port:
putty root#0.tcp.ngrok.io -P 13495
How can i use empty password in MAMP?
I tried the command:
/Applications/MAMP/Library/bin/mysqladmin -u root -p password
and edited the config php file but empty password seems not working..(every other password works fine).
What can i do to use empty password?
There is a third party app that runs Apache & MySQL from MAMP without asking for a password each time. It’s quite secure because it uses a stored password locked in the Keychain. It also quits Apache & MySQL when you quit the app itself.
Here is how to use it:
Open the Keychain Access app and click ‘+’ to add a new item. Call the item ‘MAMP’ and enter the account name and password that you use to log in to your Mac.
Download and launch the MAMP No Password app
App is here.
I develop using MAMP pro on my Mac. When I start MAMP it prompts me for a password if I use port 80. If I use a higher port it doesn't prompt me, but I have to append the port number in the URL ( eg dev.local:8888 ).
Does anyone know how to make it not prompt for password when using standard ports?
Thank you.
I've put together an app that allows you to start/stop MAMP's Apache and MySQL without the password request, even on port 80. It stores the password in Keychain, so you only need to enter it once. It has a nice icon too!
Download: http://www.46palermo.com/blog/run-mamp-without-password-easy-way/
According to a living-e rep they are considering adding an option to store the password in the keychain:
http://forum.webedition.de/phpBB/viewtopic.php?f=4&t=5517&p=12019
Update: I pestered Living-e support and got them to add it as a feature request to their bug tracker. The link is here: http://qa.living-e.de/tracker/view.php?id=3648 (requires registration) if you want to follow it.
Another update: Still following this issue. Looks like living-e moved their bug tracker, the new link to this issue is:
http://bugs.mamp.info/view.php?id=3652
It's in German but the Google translation is:
When will start and stop the server in
each case the admin password is
required if port is used as low-1024th
If we could get the password from the
OS X Keychain / keyring, allowed
themselves to avoid annoying popup
ads.
Or a German speaker's translation is:
When the Server starts/stops it will ask for the admin password each time.
If it could get the password from OS X Keychain / Keyring, the annoying popup could be avoided.
As found on Macworld and already mentioned by Tom in the other answer there is a way with applescript! Downside is you have to save your user credentials in plain text.
Open AppleScript Editor
Enter the following code replacing YOURPASSWORD and YOURUSERNAME with your user credentials
Save it as application. You might tick run-only to prevent other users from reading the plain text as a small security measure
do shell script "/Applications/MAMP/bin/startApache.sh &" password "YOURPASSWORD" user name "YOURUSERNAME" with administrator privileges
do shell script "/Applications/MAMP/bin/startMysql.sh > /dev/null 2>&1"
There might be an issue with the correct file path as MAMP apparently changed startmySQL.sh to startMysql.sh in some version, so double check if it's not working!
You can put the new application in the Login Items (System Preferences -> Users & Groups -> Login Items), so the Apache server and MySQL start automatically without even showing up the MAMP-App at startup (silent start).
In response to the commands that were posted:
1) Run MAMP on port > 1024
Running all of the servers on MAMP (nginx, apache, mysql) with port ranges above 1024 allows the Mac OS X account you logged in with to launch the services, so you will not be asked for a password in this instance. Any server that runs below port 1024 requires root privileges when being executed.
2) chmod -R a+w /tmp
This command would recursively go through all files and sub folders in /tmp and make them writable for the current user. When MAMP launches, servers create temporary files in this directory.
Also if you decide you want to run the servers below port 1024 and want a solution with applescript that does not store the password in plain text then see this link applescript password with keychain
I'm now using these two applescripts to start/stop MAMP, you can save startup script is a login item so it's always up when I boot. It does mean storing your password in plain text, as Im the only one using this machine I can live with it, better than typing in my password at least three times a day.
I bind apache to port 8080 and then use port forwarding from 80 to 8080
sudo ipfw add 100 fwd 127.0.0.1,8080 tcp from any to any 80 in
Works for me, but I'm working on making the above script permanent. So far, nothing I've tried sticks, so I just run the command above in terminal after restarting. But you can then freely start and stop MAMP without a password and use a URL without :8080 or :8888.
Its a security issue, and MacOS with its UNIX heritage like security (=Good Thing). That's why MacOS asks for passwords all the time. Not much you can do about it as far as I know.
1) Run MAMP on port > 1024
2) chmod -R a+w /tmp