it looks like I can run the script manually but its still failing to run as a service…
chris6@vmi717501:/opt/startup-scripts$ ./tx-api.sh
[cardano-tx-submit:Info:12] [2022-01-29 14:15:42.93 UTC] Running server on 0.0.0.0:8090
What would be my url to put into Nami? https://myIPaddress:port ??
I don’t run a web server, I guess I could… never needed it
http://127.0.0.1:8090 or http://localhost:8090 should work.
Anyone got this working at the moemnt? I started submit-api and Nami sends HTTP request to my submit-api server but it’s using OPTIONS method which is being rejected by submit-api on my relay.
Nami > Relay HTTP 544 OPTIONS /api/submit/tx/ HTTP/1.1
Relay > Nami HTTP 182 HTTP/1.1 405 Method Not Allowed
My understanding is that Nami should be sending POST request instead of OPTIONS. Any ideas?
using nginx Nami sends POST but we still don’t have the correct api response working
Our Nami > relay POST /api/submit/tx HTTP/1.1" 500 31
any insights would be helpful
continued testing
Nami > http://relayIPaddress/api/submit/tx
Relay log > 76.101.89.155 - - [31/Jan/2022:10:16:30 -0500] "POST /api/submit/tx
Relay console > [cardano-tx-submit:Info:12] [2022-01-31 15:09:49.54 UTC] Running server on 0.0.0.0:8090
Network.Socket.connect: <socket: 15>: does not exist (No such file or directory)
Ok we fixed the socket path in tx-api script but now we get socket connection refused error?
Relay console > [cardano-tx-submit:Info:12] [2022-01-31 15:09:49.54 UTC] Running server on 0.0.0.0:8090
Your submit-api runs on 0.0.0.0:8090 - I would change it to your actual IP address in the script and try again.
If the Cardano tools work like it is usual, then this should make the server listen on all interfaces of the machine:
Well I’m aware of that it should listen on all the addresses but when you troubleshot something you should not make such assumptions blindly and rule out all the possibilities one by one.
In addition I did have the very same issue but once I changed to my actual IP address of the node it was able to establish TCP connection.
Still the problem remains with Nami sending OPTIONS which is very first HTTP request after TCP handshake. Since I can’t change Nami behaviour I am thinking if it’s possible to change submit-api settings so it allows the OPTIONS method. Was searching in the documentation but couldn’t find it anywhere.
1 Like
I finally successfully submitted a custom node transaction using NAMI and one of my relays!
https://freeloaderz.io <<<< something new is loading 
1 Like
I got this error when trying to “stack” submissions using Nami custom node option in other words I tried to send a transaction before my previous transaction came back with a transaction confirmed - So DONT DO THIS! lol [2022-02-01 15:12:31.12 UTC] txSubmitPost: failed to submit transaction: transaction submit error ShelleyTxValidationError ShelleyBasedEraAlonzo (ApplyTxError [UtxowFailure (WrappedShelleyEraFailure (UtxoFailure (ValueNotConservedUTxO (Value 0 (fromList )) (Value 17870880 (fromList ))))),UtxowFailure (WrappedShelleyEraFailure (UtxoFailure (BadInputsUTxO (fromList [TxInCompact (TxId {_unTxId = SafeHash “acad3a58431122e2196990e211fa55e0bf477ce9b643992a1e5b8db00615fbde”}) 1]))))])
1 Like
which rules have you guys created on the router side? I can only create the transaction in my network. From outside I can execute the transaction. I have opened the configured port there
Did u configured also the port forwarding on ur local router?
Cheers,
yes I did ! tcp 8090
when I expose the device complete to the internet the transaction get execute. so I missing some other rule on the router.
rule on ufw… did u reloaded the ufw?
sudo ufw allow proto tcp from any to any port 8090
yes I did! if I don’t set the ufw rules correctly on the node the transaction inside my network even get execute
and the PF should be…
all trafic (0.0.0.0/0) on port 8090 send to private IP port 8090
If anyone interested my issue with submit-api and OPTIONS http request was due to enabled site access in Chrome extension menu. Since I’m paranoid I allowed Nami/CCvault only for specific sites. Please see attached screenshot. If you are also getting HTTP status code 405 -Method not Allowed check you extension settings and if necessary either enable it for all sites or add your submit-api domain of choice to the list (which I did)
Anyone have any idea why i am getting “Network.Socket.connect: <socket: 15>: permission denied (Permission denied)” when i try to submit a transaction with Nami to my AWS node.
did u opened the port on FW?