Thanks for that, i did made those changes and created two deployment, but not getting any BIDS for it.
DSEQ: 2386979 and 2386785.
Both are open but I’m not getting any BIDS for them.
akash query market bid list --owner=$AKASH_ACCOUNT_ADDRESS --node $AKASH_NODE --dseq $AKASH_DSEQ
bids:
pagination:
next_key: null
total: “0”
akash query market bid list --owner=$AKASH_ACCOUNT_ADDRESS --node $AKASH_NODE --dseq 2386785
bids:
pagination:
next_key: null
total: “0”
Any idea on why no BIDS is that because of any attribute of the yml file I’m using?
I think due to high demand there is increase in price for deployment so for specifying less pricing in deploy.yml you may not get bids!
Try increasing price in your deploy.yml file…
i have updated to deploy.yml file u can check and redeploy…
Thanks Piyush, whats the link for akash deployment ui?
You can find a list of deploy uis here: Deploy UI Tools
the most used deploy ui at the moment is the one from akashlytics
so I created another deployment using the updated deploy.yml. All steps looked fine and I was able to finalize a lease. and send deploy.yml to them.
akash query market lease list --owner $AKASH_ACCOUNT_ADDRESS --node $AKASH_NODE --dseq $AKASH_DSEQ
leases:
choose provider:
AKASH_PROVIDER=akash1vky0uh4wayh9npd74uqesglpaxwymynnspf6a4
akash provider lease-status --node $AKASH_NODE --home ~/.akash --dseq $AKASH_DSEQ --from $AKASH_KEY_NAME --provider $AKASH_PROVIDER
Enter keyring passphrase:
{
“services”: {
“web”: {
“name”: “web”,
“available”: 1,
“total”: 1,
“uris”: [
“xxxx.xxxxxxx.xxxx”,
“p14sgc81u5f7h294ml846vakoc.ingress.provider-2.prod.ewr1.akash.pub”
],
“observed_generation”: 1,
“replicas”: 1,
“updated_replicas”: 1,
“ready_replicas”: 1,
“available_replicas”: 1
}
},
“forwarded_ports”: {}
}
echo $AKASH_NODE $AKASH_CHAIN_ID $AKASH_KEYRING_BACKEND
http://XX.XX.XX.XX:26657 akashnet-2 os
echo $AKASH_DSEQ $AKASH_OSEQ $AKASH_GSEQ
2400898 1 1
Link should be: http://p14sgc81u5f7h294ml846vakoc.ingress.provider-2.prod.ewr1.akash.pub
But when I go to the link it doesn’t open, says bad ngnix server.
Logs:
ithub logs:
goroutine 1 [running]:
github.com/tendermint/tendermint/config.EnsureRoot(0x0, 0x0)
github.com/tendermint/tendermint@v0.34.9/config/toml.go:35 +0x305
github.com/cosmos/cosmos-sdk/server.interceptConfigs(0xc000ee19e0, 0xc000f497c0, 0x4, 0xc000bdf618)
github.com/cosmos/cosmos-sdk@v0.41.3/server/util.go:193 +0x936
github.com/cosmos/cosmos-sdk/server.InterceptConfigsPreRunHandler(0xc000ee7600, 0xc0000ee000, 0x7fc6b6541e58)
github.com/cosmos/cosmos-sdk@v0.41.3/server/util.go:126 +0x325
github.com/ovrclk/akash/cmd/akash/cmd.NewRootCmd.func1(0xc000ee7600, 0xc0000ea540, 0x0, 0xe, 0x0, 0x0)
github.com/ovrclk/akash/cmd/akash/cmd/root.go:83 +0x4f
github.com/tendermint/tendermint/libs/cli.concatCobraCmdFuncs.func1(0xc000ee7600, 0xc0000ea540, 0x0, 0xe, 0x0, 0x0)
github.com/tendermint/tendermint@v0.34.9/libs/cli/setup.go:118 +0x7c
github.com/spf13/cobra.(*Command).execute(0xc000ee7600, 0xc0000ea460, 0xe, 0xe, 0xc000ee7600, 0xc0000ea460)
github.com/spf13/cobra@v1.1.1/command.go:829 +0x582
github.com/spf13/cobra.(*Command).ExecuteC(0xc000d77b80, 0x2a0ed3d, 0x5, 0xc000c9d660)
github.com/spf13/cobra@v1.1.1/command.go:958 +0x375
github.com/spf13/cobra.(*Command).Execute(…)
github.com/spf13/cobra@v1.1.1/command.go:895
github.com/spf13/cobra.(*Command).ExecuteContext(…)
github.com/spf13/cobra@v1.1.1/command.go:888
github.com/ovrclk/akash/cmd/akash/cmd.Execute(0xc000d77b80, 0x2ff6348, 0xc000e88930)
github.com/ovrclk/akash/cmd/akash/cmd/root.go:117 +0x26d
main.main()
github.com/ovrclk/akash/cmd/akash/main.go:14 +0x2a
Any idea what the issue maybe?
Redeploy and wait for two minutes!
Hey is your problem solved now?
If you need any more help, feel free to ask!
Will try again in a while, but did you mean that the last deployment was successful?
Because I waited for a while but was still wasn;t able to get the image.
This seems to be only for Window/MACOS, we are trying to deploy from a linux system.
The deploy.yml you have has port 80 as 80, should that not be 5000 as 80, I’m running my server locally on that port.
expose:
- port: 80
as: 80
to:
- global: true
Also, any suggestion on having ‘https’ in docker image, running the site locally doesn’t have https enabled so thats why when the migration of that to akash cloud is going to http link.
But, the certificate is enable for that domain so when I actually go that site it an https:
Not sure if we first need to enable https on docker image and then migrate or if we switch the current Domain to point to the akash uri instead of our localhost that would solve the issue?
for https you should use custom link which can be linked to your akash uri through cloudflare: In you docker image i saw you expose port 8000 thats why i recommend using 80…
Thanks for that, any links to article which can help in setting up https:// on docker.
Just to confirm the site running at: “http://ukq2ar4kule8f5loa6qj2dag18.ingress.provider-0.prod.ams1.akash.pub/”
Is using deploy.yml of: “akashskynet/deploy2.yml at main · Developer-piyush/akashskynet · GitHub”
Thanks!
So, after the change to deploy.yml(port setting) was able to get the site going at:‘http://p14sgc81u5f7h294ml846vakoc.ingress.provider-2.prod.ewr1.akash.pub’
I was able get to my test site ‘http://www.testdatk.org/’ linked to akash URI by putting URL redirect entry in namecheap for the domain as per link(Deploy onto Akash : Setting up your Keplr Wallet | by Anthony Rosa | Aug, 2021 | Medium).
Next step was to create ssl/https going via cloudflare.
I went to cloudflare and created two nameservers: mary.ns.cloudflare.com and julio.ns.cloudflare.com
i added these entries under nameservers under custom DNS in namecheap for the domain, now I can get to site as https:// but it says “404 Not Found”
I did change the accept parameter in deploy.yml to the new domain name from what it was earlier.
updated and uploaded it via the deploy.yml which was successful,
So akash website works fine at it orignal URI.
http also worked ok when there was only URL redirects.
But after I did the cloudflare setting for nameserver it doesn’t seem to work, does it take more time or its something else you think?
First few lines from Deploy.yml:
version: “2.0”
services:
web:
image: tushcrypteddocker/tktestweb:latest
expose:
- port: 80
as: 80
accept:
- testdatk.org
to:
- global: true
Infact can ignore this, got it working.
Infact was trying another deployment with an image which was running locally on port 9090.
So I was able to push the docker image created to dockerhub(tushcrypteddocker/dacmtest:latest (image ID-d3c8676e533f).
And further to akash, the process of creating deployment, getting BIDS, confirming lease, and uploading the manifest file was all good.
We got a3cm7k8utp9dl6357eokpp3dig.ingress.provider-2.prod.ewr1.akash.pub as the URL.
but when we go to that it says Bad gateway error 503, any idea what can the the issue?
version: “2.0”
services:
web:
image: tushcrypteddocker/dacmtest:latest
expose:
- port: 9090
as: 80
accept:
- testdatk.org
to:
- global: true
profiles:
compute:
web:
resources:
cpu:
units: 1
memory:
size: 512Mi
storage:
size: 512Mi
placement:
westcoast:
attributes:
host: akash
signedBy:
anyOf:
- “akash1365yvmc4s7awdyj3n2sav7xfx76adc6dnmlx63”
pricing:
web:
denom: uakt
amount: 5000
deployment:
web:
westcoast:
profile: web
count: 1
Deployment was created under DSEQ: 2617592
Lease was created and active confirmed with: akash1vky0uh4wayh9npd74uqesglpaxwymynnspf6a4
Was able to upload the manifest as well.
Tried to confirm the URL which is as:
Status as below:
{
“services”: {
“web”: {
“name”: “web”,
“available”: 1,
“total”: 1,
“uris”: [
“testdatk.org”,
“a3cm7k8utp9dl6357eokpp3dig.ingress.provider-2.prod.ewr1.akash.pub”
],
“observed_generation”: 1,
“replicas”: 1,
“updated_replicas”: 1,
“ready_replicas”: 1,
“available_replicas”: 1
}
},
“forwarded_ports”: {}
}