I'm using Transmission 2.52 on a Debian server. The only thing I changed in settings.json is username and password. When I try to connect, it ask me my login details but after this, it says:
409: Conflict
Your request had an invalid session-id header.
I looked over the internet but I didn't find anything good. I tried different url like:
host:9091/transmission/
host:9091/transmission/web/
host:9091/transmission/web/#files/
Always the same error.
I am using Debian 4.7.2-5 and transmission 2.52
Any solution?
Thank you
I've just experienced this problem myself, and found a solution here:
http://www.raspberrypi.org/forums/viewtopic.php?f=74&t=22013
Basically, remember to add the trailing '/' on the end of your transmission url, for example:
This works:
http://10.0.0.4:9091/transmission/web/
But this gives the 409: Conflict message:
http://10.0.0.4:9091/transmission/web
Related
platform: wordpress + woocommerce + PDF Product Vouchers
When generating a voucher, an error sometimes pops up:
could not generate voucher pdf: cannot create voucher: incorrect magic number (0)
What could be the problem?
You're getting this error because your hosting server has an incorrect SSL certificate set for OpenSSL, so when this third-party library dompdf (which is being used by SkyVerge) sends a file_get_contents() request to this URL to load Google fonts, it throws this error SSL: Connection reset by peer.
The quick solution to fix it is to put this snippet below in your functions.php or any code snippet plugin like WPCode, which will unload Google Fonts and use the default fonts:
add_filter('wc_pdf_product_vouchers_available_google_fonts', function(){
return [];
});
If you mean Skyverge product, it's actual issue. Skyverge is looking for a solution. But if ASAP, then try to replace with PDF plugin version 3.8, not 3.9 and newer.
The problem was caused by the plugin: mail log. After disabling, everything works without errors.
Probably the problem is in the incorrect function of sending letters.
I am new to this topic. I have deployed my app to Azure (following the tutorial from Autodesk). When I try to press to the login to BIM360 is return an error 500 (internal Server Error). I have changed the FORGE_CALLBACK_URL = "htttp://forgeSample1234.azurewebsite.net/api/forge/callback/oauth"
The code has no problem when in localhost.
Does anyone has the same problem?
Please note that when updating the callback URL, you actually have to change it in two places:
in your code (that's typically the FORGE_CALLBACK_URL)
in your Forge app page in https://forge.autodesk.com/myapps
And of course, the URL has to match exactly in both places.
Also, it looks like there might be a typo in your URL: you say htttp instead of http, and I'm also wondering if you shouldn't be using https?
By default apiconnect adds security to be required on all the paths. How can I allow a hit on a path without requiring authentication first?
I've tried unchecking the "Use API security definitions" in the Security section of on my User.count path, but when I use the browser on the URL https://localhost:4002/api/Users/count I get back
Error
401 Authorization Required
code: AUTHORIZATION_REQUIRED
Error: Authorization Required
at D:\PeteSoft\node\test3\node_modules\loopback\lib\application.js:433:21
at D:\PeteSoft\node\test3\node_modules\loopback\lib\model.js:359:7
at D:\PeteSoft\node\test3\node_modules\loopback\common\models\acl.js:536:16
at D:\PeteSoft\node\test3\node_modules\async\dist\async.js:3888:9
at D:\PeteSoft\node\test3\node_modules\async\dist\async.js:473:16
at iteratorCallback (D:\PeteSoft\node\test3\node_modules\async\dist\async.js:1064:13)
at D:\PeteSoft\node\test3\node_modules\async\dist\async.js:969:16
at D:\PeteSoft\node\test3\node_modules\async\dist\async.js:3885:13
at D:\PeteSoft\node\test3\node_modules\loopback\common\models\acl.js:518:17
at D:\PeteSoft\node\test3\node_modules\loopback\common\models\role.js:447:21
at process._tickCallback (internal/process/next_tick.js:61:11)
How can I get the count returned instead of the Authorization Required error?
If you are using the free version, you have to include the IBM client Id (and IBM client secret is optional)..
However, the Authorization error can be catched, so if you properly configure the catch to capture that error, you could work withouth the IBM Client id.. (it is a bad practice, but might solve your problem).
Catch Auth Error
If you want to work with out those keys, you have to buy the product, and in the Design Tab, it will allow you to remove it...
I created a fresh rails-api app and added an address model to it and then installed rails_admin. And whenever I try to add rows, I get 422s
I can see that CSRF token has been sent in the JSON, but it says its invalid.
Processing by RailsAdmin::MainController#new as HTML
Parameters: {"utf8"=>"✓", "authenticity_token"=>"9PP0EREx/cTK2TVtMp38ao/U9QCu6pjwmvV4fxIGEwTjZvGUfTcz7hpWL85UR/7qO3w+kytA2HD98+u7yiy3wg==", "address"=>{"door_no"=>"229", "street"=>"", "area"=>"", "city"=>"", "state"=>"", "pin"=>"", "code"=>""}, "return_to"=>"", "_save"=>"", "model_name"=>"address"}
Can't verify CSRF token authenticity.
Completed 422 Unprocessable Entity in 0ms (ActiveRecord: 0.0ms)
ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken)
What could be wrong? Something in the gem maybe?
I initially thought that the issue was same that I encountered some months before, posted on Github, however even after downgrading to 1.1.0 I had same issues. Currently I'm on Rails 5.1.2 and Rails Admin 1.2.0.
Setting config.api_only = false solves the problem
api-only mode seems to clash with some csrf verification stuff, which started to work pretty perfect as soon as I changed the flag.
I'm integrating Google's login with a Flask site using Flask-OAuth.
Everything is working fine. I can authorise the login and get a token back etc without any difficulties. But when I use Flask-OAuth's get method to request the logged in user's email address I get an error saying:
TypeError: Unicode-objects must be encoded before hashing
I'm using Python3 and this has the smell of a Python version issue but I can't figure out what I'd need to change.
The code I'm using is this:
def get_additional_data(self):
access_token = session.get('oauth_token')
headers = {'Authorization': 'OAuth ' + access_token[0]}
return self.service.get(
'https://www.googleapis.com/oauth2/v1/userinfo', None,
headers=headers)
I'm not sure what I can encode in that request. Even if I don't pass the headers I get the same error (rather than an invalid request or something like that).
I've run 2to3 on oauth2/__init__.py and the tweaks is suggests are very minor and shouldn't prevent the code from running in Python 3. Also, everything else OAuth2 related is working.
The bad news is that the solution to this problem is switching to Flask-OAuthlib.
The good news is it required very few changes from Flask-OAuth to get it working.