I am trying unsuccessfully to publish from SBT into a Nexus repository running on my network. Attempts to publish fail with a forbidden error
If I look at the Nexus side of things with trace debugging on, I can see the request, but there is no Authorization header in the request.
This is my build.sbt
And this is my credentials file
I have used curl to see what the Realm should be, which hopefully I have reflected in my credentials file
But nothing I do seems to get the Authorization header in the PUT request. Is there something obvious I am missing? I feel like I am spinning my wheels.
Thanks for any help
This did end up being how I had set up my files. My build.sbt file was fine. However, in my credentials, my Host value contains a port, which was confusing the IvyAuthenticator. I ended up seeing this error message when running through sbt shell in IntelliJ
My issue was that, in my credentials file, my host ended with the ":8081" value, and it looks like IvyAuthenticator was using the host name without the port information.
So, after updating my credentials file, so that the host value was just the machine name without any port details, my publish succeeded.
Related
So I have my Next.JS app hosting on Lightsail with Nginx proxy, I've just done setupping the domain for my app and it's already online. Somehow when I try to log in it's giving me an error saying "Error: Callback for provider type credentials not supported"
But it works when I try to open and log in with the public IP. I guess it's something wrong with the Nginx configuration but I'm not sure which one. Maybe someone can help me with this issue?
I tried to create a custom server from Next.JS and already tried to change some Nginx configuration but it still doesn't work
Like the tutorial, I deployed the tomcat server step by step, and then used postman to test the back-end login function interface, but kept reporting errors, and at the end of the terminal it printed out :
Having failed to acquire a resource, com.mchange.v2.resourcepool. BasicResourcePool#2bda742d is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.
The complete output in the terminal in idea is:
enter image description here
the error on postman show that:
enter image description here
it was just download all the time and have no result, and I can ensure the url is right.
I will appreciate it if you can answer me.
It seems that the password of the database root account was wrong, maybe you should check your configuration file.
I'm trying to find out why I can't publish scala packages to a Maven repository (Azure Artifacts, see https://github.com/sbt/sbt/issues/5483)
I'm receiving a 203 HTTP code which causes SBT to fail the publish task.
I'm hoping to get additional info by inspecting the Warning HTTP header that - hopefully - Microsoft has added to the HTTP response but can't figure out how to configure SBT to print them on the console (setting logLevel := Level.Debug didn't help)
The error 203: Non-Authoritative Information seems like a authorization issue.
Please try encoding your PAT to base64 format to use Basic Authentication. Please check below example to get the BASE64 authorization with PAT in powershell script.
$PAT="***"
$base64AuthInfo= [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(":$($PAT)"))
Please check out this similar thread, and this thread to get a correct basic authorization string
Hope above helps!
I have a file in my folder and I want to send it to my Embedded Linux device via FTP (much like this and this and this). I know the step-by-step to do it, but I'm failing when it comes to creating the correct QUrl for it: when I call ''put'', I always get the error 301:
QNetworkReply::ProtocolUnknownError 301 the Network Access API cannot honor the request because the protocol is not known
As details, I want to save the file in a specific directory located inside a SD Card in the device, /media/mmcblk0p2/bin, and the connection doesn't have, at least for now, a password and user name defined¹. Also interesting to notice that I'm not being able to connect myself via FTP using Terminal; it always says "421 Service not available, remote server has closed connection", which is not the same problem AFAIK. (Btw I'm being able to connect via SSH using FileZilla, so it's not a hardware/physical problem)
So where is the problem? I have exactly the same code as in the mentioned links. As for now, the link I'm using is
ftp://10.1.25.10/media/mmcblk0p2/bin/center.png
(when returning the QUrl object with QDebug) and I'm not being able to make it work.
Any help would be appreciated.
¹: Btw I remember reading somewhere that when one doesn't use a user name for connecting to FTP, the system only allows the client to connect to the /ftp folder. Is that true? In that case, just calling QUrl::setUserName("root"); would suffice?
I finally discovered my problem: since I was copying the code from examples of upload to HTTP servers, I was using the function "post", specific for HTTP, instead of "put" which was the correct function to use.
Regarding the QUrl, I used QUrl urlTemp("//10.1.25.10/test.info"); while telling it to use ftp with scheme, urlTemp.setScheme("ftp");.
I've installed gitorious on CentOS 6 32bit via getgetorious.com's installer. I went ahead and edited the gitorious.yml with my host name "git.mydomain.com". Restarted gitorious with /usr/bin/restart_gitorious.
I have checked the conf.d/gitorious.conf file for nginx and it shows the server name as my "git.mydomain.com".
When I try to login I get redirected back to the homepage and nothing happens. I checked the headers being sent from the server and the cookies are for "www.mydomain.com" instead of "git.mydomain.com"
I have a server block in my nginx.conf for "www.mydomain.com" which points to a completely different directory. I can't figure out how and why the cookies are being set to www instead of git.
Here's paste of my headers. I've replaced my actual domain with mydomain.com.
http://pastebin.com/Lu0txrtR
I'm also seeing this error in the production.log file
WARNING: Invalid request host 'git.fruition.company'. Session cookies
will not work
I have made the following changes to my gitorious.yml file.
# Host the ./script/gitorious script should use: client_host:
git.fruition.company
# Host which is serving the gitorious app, eg "gitorious.org"
host: git.fruition.company
I have also tried setting the hostname using the provided shell script to no avail.
I can't figure out where or why the cookies are being set to www instead of git.
Any help would be greatly appreciated.
I ended up running the install script again and create a new user. Everything seems to work now.