I've been using JFrog Artifactory on JFrog Cloud for some time, and everything worked fine. For the past day, I've started getting a lot of 504 Gateway Timeout responses from the Artifactory service when trying to download artifacts. This breaks CI/CD processes and prohibits developers from doing their job.
I looked at the service logs on the Artifactory UI, and nothing seems out of the ordinary there. Only successful requests and responses appear there. According to the JFrog Cloud Status page, all systems are operational, so there is no clue.
Is there a way to troubleshoot this issue via the web UI or the JFrog CLI? Has anyone encountered a similar issue?
Edit: Some API requests from the web UI also receive a 504 Gateway Timeout.
The issue turned out to be a server-side issue on the Azure infrastructure that ran our Artifactory server. The JFrog team successfully resolved it.
Related
I created a new app repository in Github, built on the Meteor platform. I am having significant difficulty deploying the app to my DigitalOcean droplet, however. I am trying to connect my Github repository to the droplet and to deploy that to my domain. I am trying to do this in SSH using puTTy; however, after setting up a root account and password, I am unable to log in through SSH. I receive the following error: disconnected: no supported authentication methods available (server sent:publickey)
Does anyone know why this error is coming up? I have looked through more tutorials for deploying a meteor app on digitalocean than I care to admit, but they all seem to take different approaches and many are outdated. Any advice would be greatly appreciated!
Thank you
I reckon the easiest way is to use meteor up. It's a very simple process, and you don't need to be continually sshing into your target server, with all the hassles involving ssh keys.
In my experience, once you have it set up, it's a very painless process, and you can deploy with a simple command each time.
http://meteor-up.com/
It looks after the following:
Setting up your server with docker instances
Creating SSL certs using Let's encrypt
Building your app, bundling it, transferring it
Starting the app
Rolling back if it doesn't work
There is some trust involved, but it's worth it for a seamless deployment scenario
I was out of town and when I returned my server was off due to a power failure. All systems are functional but I can no longer log into Alfresco Community Edition. I have looked at several forums, but no real solutions.
There are a number of things you need to check before we can help you. These include things like:
Is the server running?
Can you connect to it via SSH?
Do you have a web proxy (like Apache or Nginx) installed?
Can you grep for that process?
Can you hit the web proxy?
Can you grep for the tomcat process?
Do you see anything in the logs?
Can you hit the Alfresco webapp on 8080?
Can you hit the Share webapp on 8080?
Is the database running?
If your content store storage is on a mount point, is the volume mounted?
Can you browse the content store directory?
I used Meteor Up (MUP) to deploy my meteor app to a Digital Ocean droplet. I had some problems with deploying it the first time but I solved all of them and I got it working. I then made some updates to my app but when I deployed it again the page says "This webpage is not available". I have tried re-deploying the app on new droplets with different IP addresses but the same happens. I have run mup setup on each new droplet. It always says success for the setup and for the deployment but nothing shows up.
Can anybody tell me what I have done wrong?
It's likely there is some kind of error with your app, probably not related to deployment if it the issue occurs in the way your describe it.
You'll have to check your app's server side logs for a bit more info:
mup logs -f
I have a Windows VM in Azure that I'm using for VS2015 experiments.
Google Drive is unable to contact update servers to finish its own installation (despite Chrome/Omaha working fine).
Apparently, I also can't clone git repos over ssh, even though HTTPS seems to be working.
Disabling the Windows Firewall does not seem to remedy these issues.
Suggestions?
You have to open endpoints on the vm. HTTPs and HTTP are open. If you need other ports...then you need to find them and open them as endpoints. My guess is that's what is happening here.
I am new to Azure Accelerator for web roles I have performed each step on the guidance from the net but I am getting an error when I try to deploy my website.Everything is rechecked by me WMSvc is running and is set to auto and username and password is correct but I dont understand where is the problem.
Error 1 Web deployment task failed.(Remote agent (URL http://2f96c9ab6cda4281bcf25a899d66955d.cloudapp.net/MSDEPLOYAGENTSERVICE) could not be contacted. Make sure the remote agent service is installed and started on the target computer.) Make sure the site name, user name, and password are correct. If the issue is not resolved, please contact your local or server administrator. Error details: Remote agent (URL http://2f96c9ab6cda4281bcf25a899d66955d.cloudapp.net/MSDEPLOYAGENTSERVICE) could not be contacted. Make sure the remote agent service is installed and started on the target computer. An unsupported response was received. The response header 'MSDeploy.Response' was '' but 'v1' was expected. The remote server returned an error: (401) Unauthorized. 0 0 QuickMVCdep
Please help me to find the solution so that I can deliver my project to Client.
I have run into the same issue.
It appears that the Publish action from the VS Azure tools will set up the MSDeploy correctly as part of the deployment process, but creating a package from VS and then upgrading the server using the Azure portal will not. Which is a bummer since the VS Publish action deletes the deployment and then recreates it, which will reassign your VIP address.
I haven't been able to pinpoint the difference, but one thing I've noticed is that if you do a Publish from VS, MS Web Deploy 2.0 will be installed for you, whereas I don't believe it is when you run an Upgrade. That said, I've never managed to manually install/configure the right bits on an Azure server to enable MSDeploy (I suspect that there is some LB/firewall configuration that happens outside of the host to allow traffic to 8172).
All in all, MSDeploy is useful enough during development that I prefer that pain (which requires me to change my A record in my DNS every time I do a major upgrade) over the alternative (Upgrade using the portal and lose the ability to use MSDeploy).
I would love to learn of a solution where we can have our cake and eat it too (an upgrade package that allows MSDeploy'ing a web role).