JFrog artifactory gives 403 Forbidden when started on localhost - artifactory

Recently I installed jfrog artifactory on my machine as per installation instructions on the official website and couple of youTube videos.
When tried to start artifactory in local browser with http://localhost:8081 (as per artifactory website) I am getting 403 Forbidden
I tried couple of browsers and disabling the proxies in browser but it did not work

I tried using different post and scanning the artifactory start log and tried port 8040 (http://http://localhost:8040) instead of 8081 and it worked. Probably official document is mentioning incorrect port

Related

Artifactory Custom Base URL give 404 page not found error

Running Artifactory Pro 7.2.1 in a Docker container.
I can access Artifactory via http://${IP}:port, but when I try to access Artifactory login page or repos I setup via the Custom Base URL I setup https://${hostname} I get a 404 page not found.
I can ssh to the host name and log into the Artifactory server (Linux Centos VM).
Any help would be appreciated.
The Custom Base URL in Artifactory doesn't configure any internal redirections or configures the application to listen on another port.
Unless you have a reverse-proxy to listen on the configured Custom Based URL and redirect to the Artifactory IP and port, there is probably nothing to resolve them.
A possible approach to achieve this can be using NGINX.

localhost.run wordpress ssh tunneling

I need to show a preview of a wordpress project to a client. I want to setup a tunnel to expose the macOS apache server instance. In past I was using ngrok but with wordpress it requires some configuration and I don't want to waste time in plugins installation ecc.
I've tried with Serveo, but it seems to be offline at the moment, after a little bit of research I've found localhost.run that offer the same service of Serveo.
How I can find the actual port of the embed apache server of my macOS and how I will expose wordpress without plugins installation?
I've tried with this command
ssh -R 80:localhost:8080 ssh.localhost.run
but it will give an error when I open the tunneling url:
Something went wrong opening the port forward, check your SSH command output for clues!
Try setting the Apache "httpd.conf" to
Listen 8080 and
ServerName localhost:8080

HTTPS not working with WordPress click to deploy

I installed WordPress in Google Cloud Plattform using the feature "Click to Deploy".
But I need my website work with HTTPS. So I get a certificate with Let's encrypt and I followed the instructions in https://cloud.google.com/appengine/docs/standard/python/console/using-custom-domains-and-ssl to install it. All the process was successful but when I try to use my site with HTTPS I get the error "the site refused the connection".
This page https://cloud.google.com/solutions/connecting-securely says an option is use load balancing, but I believe I don't need that.
I applied this others instructions unsuccessfully:
www.wpbeginner.com/wp-tutorials/how-to-add-ssl-and-https-in-wordpress
www.elegantthemes.com/blog/tips-tricks/how-to-install-wordpress-on-google-cloud-and-why-thats-awesome
stackoverflow.com/questions/30075971/google-cloud-platform-cannot-get-https-ssl-working-on-wordpress-instance
My site works fine with HTTP.
I resolved my problem with this video: https://www.youtube.com/watch?v=7kLvD2mlmlk
The difference is I had to upload my crt and key files generated by Let's encrypt.
It was very difficult for me because I am not familiar with linux.
Regards.

NexusToArtifactory tool , unable to give artifactory url

I am using nexus2artifactory tool to migrate from Nexus to Artifactory. In the initial setup menu, while giving the artifactory URL, Nexus2Art migrator tool is showing below error:
Unable to access artifactory URL. and errors in lines 435,548,473,407,556 of urllib2.py
HTTP Error 503 : Service unavailable
Artifactory URL is accessible in browser and running successfully. But the tool is not able to recognize artifactory. I have checked the log files artifactory.log, request.log, access.log and there is no errors in the log files. Please give me suggestions to resolve this issue.

MAMP "Extras" Wordpress site causes error ERR_CONNECTION_REFUSED

In short, I can create a new MAMP Pro 3 host with success and then download and install Wordpress 4.0 via MAMP Pro's "Extra's" feature also seemingly with success (no errors, ) ...yet it doesn't turn out that way as the browser says, "Error code: ERR_CONNECTION_REFUSED".
Full Details: Hi, I've just installed MAMP Pro for the first time on Mac OS 10.9.5 with all the default settings, the WebStart page loaded in the browser, php looks to be running fine. The problem I'm having occurs when running a preliminary test of MAMP by trying the Extras feature and installing Wordpress 4.0. I get no indication that anything went wrong with the default install yet clicking the button next to the Server Name "Open the hosts web page in a browser"... I am greeted with an error in Google Chrome, Firefox, Safari, etc....
"This webpage is not available. Google Chrome's connection attempt to was rejected. Error code: ERR_CONNECTION_REFUSED
Google Chrome's connection attempt to testwpextra.dev was rejected. The website may be down, or your network may not be properly configured.
Check your Internet connection
Allow Chrome to access the network in your firewall or antivirus settings.
Check your proxy settings
"
I'm not using a proxy, I am running apache as my local user and have confirmed the document root is owned by the same user (with read/write permissions), I turned off firewall/littlesnitch just to be sure, same result in various browsers.
I read some fella saying something about setting up his host with IPv6 but I'm using the MAMP control panel to manage the process for me and don't see settings of that nature. Maybe this is done via the Extended tab with directory or VirtualHost parameters, I don't know... wish I did. Please help! Thanks!
I solved my problem by changing MAMPs ports from the default 8888 etc... to 80,443,3306 (on MAMPs General tab). Now all my includes are broken because MAMP doesn't allow "php_value" in htaccess files...one step at a time i guess. =]

Resources