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.
Related
I need to redirect HTTP to HTTPS, and www to non-www, with the Azure AppService version of Wordpress. This version uses the wordpress-alpine-php docker image, running nginx version 1.20.2.
I think I need to add a server block to nginx.conf, but I am not sure which version of this file it's using. I see the file in these locations.
/etc/nginx/nginx.conf
/home/site/wwwroot/nginx.conf
I've tried both of them, but neither seems to work. The one under etc doesn't seem to persist a container reload. I do know about copying the correct version and then reloading nginx with a startup command, as described in this Microsoft article.
Is nginx.conf the place to do this?
Which versions of the file is this using at runtime?
Is there a better way to do this with the azure app service?
we are using Artifactory 6.20.0 in docker-compose mode. Stack is up and running fine. But I am not able to edit the "Public Server Name" in HTTP settings. It is greyed out.
How can I change it?
From Which file TomCat picks these values?
As per my understanding If I change Http settings and use nginx or tomcat. Still my Artifactory is reachable using same address which embedded Tomcat has provided and nginx will be only used for the path based routing. or nginx takes care of both parts?
Please note 'HTTP settings' in Artifactory UI is a template to generate the reverse proxy configuration according to provided fields and you can use the same snippet downloaded and install directly in the corresponding directory of your reverse proxy server.
Answers to your queries:
Embedded tomcat will not pickup any values from this template, it runs on 8081 (over http) by default.
As stated above, changing Http settings in UI will not help as it is a simple template. You must have a reverse proxy installed and place the required configuration on reverse proxy directories in order to access Artifactory over a DNS(http/https). Please refer to Configuring Reverse Proxy wiki page for more details.
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
I have a bitnami WordPress instance using AWS lightsail. I need to migrate the site to another identical AWS instance. I created a PHP installer from the first instance using the Wordpress Duplicator plugin.
I then uploaded the file onto the new server to a folder (opt/bitnami/apache2/htdocs/).The instructions I've seen online they say I just need to navigate to the location of the installer in a browser and it will run. However, when I attempt to access the PHP file from a browser I just get an error on the front-end saying:
OOPS! THAT PAGE CAN’T BE FOUND
I have seen suggestions online that the installer be placed into a public folder called html_public but my instance doesn't have a folder like that. I changed the access rights to the folder, and the installer, to be full rw access.
Any ideas how I can get this to work?
You must config the Security Groups firewall to open the HTTP port.
Open the Amazon VPC console at [https://console.aws.amazon.com/vpc/]
On the Inbound Rules tab, choose Edit the port range 80, 443 - Source: Anywhere - IP Address: 0.0.0.0/0 and Save.
We have JIRA-Software 7 running on a custom docker machine with a Postgres DB and nginx as a reverse proxy (SSL). The custom domain is https://jira.url.de and is working so far. Installation has not been a problem.
But now i wanted to install a plugin and i get the following error:
An unexpected error has occurred. Please refer to the logs for more information.
First of all where can i find the logs?
Second - i found out that if i click on "Manage Add-on i will be directed to a 500 error on http://127.0.0.1:8080/plugins/servlet/upm
I read somewhere about configuring the server.xml file in order to correct the plugin url. But how can i edit this file? I can not find it inside the docker container.
UPDATE
if i try to update the Atlassian Universal Plugin Manager Plugin i get the following console Notice:
[blocked] The page at https://jira.url.de/plugins/servlet/upm was not allowed to display insecure content from http://127.0.0.1:8080/rest/plugins/self-update/1.0/.
If by clicking to Manage Add-ons you will go to loopback IP Address, most likely your Base URL is not configured properly. Thus, I would say ensure that your base URL configured properly.
Other than that, you need to ensure that you do have proxyName and proxyPort configured in server.xml file. I would say check this document for full details about Nginx configuration.
Lastly, installing plugin from UPM requires access to Marketplace. Thus, you need to ensure that your docker image is able to communicate with Atlassian Marketplace.
Hint:
Monitor atlassian-jira.log file which is in home directory of the jira. That way, you will get better information from the logs.