{ "id": 613906, "title": "could not connect to 3LC service red banner in the dashboard", "url": "/competitions/the-3lc-cotton-weed-detection-challenge/discussion/613906", "author_name": "", "post_date": "2025-10-30T17:38:36.627171300Z", "votes": null, "comment_count": 5, "views": 0, "content": "

I followed the steps given in the link https://github.com/3lc-ai/3lc-with-colab, but still getting the red banner. i am using colob pro but exhausted my limits which will be renewed in couple of days. is the red banner is displyed in the dashboard beacuse of free resources of colob ?

", "messages": [ { "id": "3309005", "postDate": "10/30/2025 17:38:36", "content": "

I followed the steps given in the link https://github.com/3lc-ai/3lc-with-colab, but still getting the red banner. i am using colob pro but exhausted my limits which will be renewed in couple of days. is the red banner is displyed in the dashboard beacuse of free resources of colob ?

", "rawMarkdown": "I followed the steps given in the link https://github.com/3lc-ai/3lc-with-colab, but still getting the red banner. i am using colob pro but exhausted my limits which will be renewed in couple of days. is the red banner is displyed in the dashboard beacuse of free resources of colob ?", "votes": null }, { "id": "3309029", "postDate": "10/30/2025 19:02:11", "content": "

@gokulakrishnanp thanks for trying out 3LC, and sorry you have run into trouble.

\n

The red banner in the dashboard means that it cannot reach the object service, even though your colab screenshot appears to show it is running just fine.

\n

From the dashboard screenshot, it looks like the ngrok URL for the object service may have accidentally ended up with an unintentional space in it, i.e. it should start with \"deistic\" and not \"deisti c\". Maybe an extra character was included when copying from the colab terminal?

\n

\"\"

\n

Can you check the address bar and see if there is a space there (either an actual space or perhaps an encoded %20) and remove it if so and press enter? I think the URL you are using for this example would look like:\nhttps://dashboard.3lc.ai/?object_service=https%3A%2F%2Fdeistic-angle-nonprimitively.ngrok-free.dev

\n

Note that when you run the object service again, it will get a different URL from ngrok.

", "rawMarkdown": "gokulakrishnanp thanks for trying out 3LC, and sorry you have run into trouble.\n\nThe red banner in the dashboard means that it cannot reach the object service, even though your colab screenshot appears to show it is running just fine.\n\nFrom the dashboard screenshot, it looks like the ngrok URL for the object service may have accidentally ended up with an unintentional space in it, i.e. it should start with \"deistic\" and not \"deisti c\". Maybe an extra character was included when copying from the colab terminal?\n\n![](https://www.googleapis.com/download/storage/v1/b/kaggle-forum-message-attachments/o/inbox%2F27793746%2Fb6ee056e74e179dfc98e21703db9b431%2FScreenshot%202025-10-30%20135155.png?generation=1761850442555357&alt=media)\n\nCan you check the address bar and see if there is a space there (either an actual space or perhaps an encoded %20) and remove it if so and press enter? I think the URL you are using for this example would look like:\nhttps://dashboard.3lc.ai/?object_service=https%3A%2F%2Fdeistic-angle-nonprimitively.ngrok-free.dev\n\nNote that when you run the object service again, it will get a different URL from ngrok.", "votes": null }, { "id": "3309203", "postDate": "10/31/2025 07:26:42", "content": "

@kellywalker3lc Thank you so much for addressing the issue, yes that's correct because of the space. now the red banner is gone after copy pasting it instead of right click 'go to' over the link inside terminal. but still the log got an error \"https://deistic-angle-nonprimitively.ngrok-free.dev/status: Invalid HTTP response (\n<html class=\"h-full\" lang=\"en-US\" …)\" could you help me how to rectify this error ? i also want to see public examples to explore the dashboard.

", "rawMarkdown": "kellywalker3lc Thank you so much for addressing the issue, yes that's correct because of the space. now the red banner is gone after copy pasting it instead of right click 'go to' over the link inside terminal. but still the log got an error \"https://deistic-angle-nonprimitively.ngrok-free.dev/status: Invalid HTTP response (\nI am actually working with another user on the same issue:\nhttps://www.kaggle.com/competitions/the-3lc-cotton-weed-detection-challenge/discussion/612346#3307671

\n

At this point, it is still a mystery, but I am hoping to make some progress today.

\n

Could you do the same thing I have asked the other user to do?

\n
\n

Hmm…that is surprising that you get back the expected pages when browsing directly but that the dashboard does not.

\n

Can you do the following:

\n \n

Thank you for your patience with all of this. I am really hoping we can get to the bottom of the mystery.

\n
", "rawMarkdown": "I am actually working with another user on the same issue:\nhttps://www.kaggle.com/competitions/the-3lc-cotton-weed-detection-challenge/discussion/612346#3307671\n\nAt this point, it is still a mystery, but I am hoping to make some progress today.\n\nCould you do the same thing I have asked the other user to do?\n\n> Hmm...that is surprising that you get back the expected pages when browsing directly but that the dashboard does not.\n> \n> Can you do the following:\n> - Run the object service using ngrok and loglevel DEBUG as before\n> - Browse to the object service \"live\" and \"status\" endpoints directly and post screenshots of the browser with address and page contents\n> - Open the developer tools network tab\n> - Browse to the dashboard URL (that has object_service=...)\n> - Post a screenshot of the Log window with its errors\n> - Select the requests going to the object service (\"status\" and any pre-flight requests) in the developer tools network tab, inspect the request/response headers, status code, any redirects, and contents if possible; post screenshots of all you can\n> - Post your 3LC log; we should see it serving the \"live\" and \"status\" requests you entered directly but then presumably nothing after since the dashboard requests seem not to make it\n> \n> Thank you for your patience with all of this. I am really hoping we can get to the bottom of the mystery.", "votes": null }, { "id": "3309472", "postDate": "10/31/2025 19:26:37", "content": "

You may be interested to see that the other user figured out the cause of the issue. There was an ngrok warning getting in the way.\nhttps://www.kaggle.com/competitions/the-3lc-cotton-weed-detection-challenge/discussion/612346#3309407

\n

I have asked for some more details about the ngrok warning. If/when those are posted, it may help us understand if you are having the same issue.

\n

Also, that user posted a notebook using a different solution - cloudflare instead of ngrok - that you might also use to work around your issue.

", "rawMarkdown": "You may be interested to see that the other user figured out the cause of the issue. There was an ngrok warning getting in the way.\nhttps://www.kaggle.com/competitions/the-3lc-cotton-weed-detection-challenge/discussion/612346#3309407\n\nI have asked for some more details about the ngrok warning. If/when those are posted, it may help us understand if you are having the same issue.\n\nAlso, that user posted a notebook using a different solution - cloudflare instead of ngrok - that you might also use to work around your issue.", "votes": null }, { "id": "3336236", "postDate": "11/18/2025 12:02:57", "content": "

We have found a bug in the logic that sets the header that allows for bypassing the NGrok warning page. Sometime after we added that original logic, NGrok made it so free accounts use more than one base domain, and we were only checking for one in particular. A fix will be available in the next 3LC Dashboard release, coming in the next couple of days. Sorry for the trouble and for the confusion.

", "rawMarkdown": "We have found a bug in the logic that sets the header that allows for bypassing the NGrok warning page. Sometime after we added that original logic, NGrok made it so free accounts use more than one base domain, and we were only checking for one in particular. A fix will be available in the next 3LC Dashboard release, coming in the next couple of days. Sorry for the trouble and for the confusion.", "votes": null } ], "comments": [ { "id": 3309029, "author_name": "kellywalker3lc", "author_url": "", "post_date": "10/30/2025 19:02:11", "content": "

@gokulakrishnanp thanks for trying out 3LC, and sorry you have run into trouble.

\n

The red banner in the dashboard means that it cannot reach the object service, even though your colab screenshot appears to show it is running just fine.

\n

From the dashboard screenshot, it looks like the ngrok URL for the object service may have accidentally ended up with an unintentional space in it, i.e. it should start with \"deistic\" and not \"deisti c\". Maybe an extra character was included when copying from the colab terminal?

\n

\"\"

\n

Can you check the address bar and see if there is a space there (either an actual space or perhaps an encoded %20) and remove it if so and press enter? I think the URL you are using for this example would look like:\nhttps://dashboard.3lc.ai/?object_service=https%3A%2F%2Fdeistic-angle-nonprimitively.ngrok-free.dev

\n

Note that when you run the object service again, it will get a different URL from ngrok.

", "votes": null, "replies": [ { "id": 3309203, "author_name": "gokulakrishnanp", "author_url": "", "post_date": "10/31/2025 07:26:42", "content": "

@kellywalker3lc Thank you so much for addressing the issue, yes that's correct because of the space. now the red banner is gone after copy pasting it instead of right click 'go to' over the link inside terminal. but still the log got an error \"https://deistic-angle-nonprimitively.ngrok-free.dev/status: Invalid HTTP response (\n<html class=\"h-full\" lang=\"en-US\" …)\" could you help me how to rectify this error ? i also want to see public examples to explore the dashboard.

", "votes": null, "replies": [ { "id": 3309311, "author_name": "kellywalker3lc", "author_url": "", "post_date": "10/31/2025 12:31:51", "content": "

I am actually working with another user on the same issue:\nhttps://www.kaggle.com/competitions/the-3lc-cotton-weed-detection-challenge/discussion/612346#3307671

\n

At this point, it is still a mystery, but I am hoping to make some progress today.

\n

Could you do the same thing I have asked the other user to do?

\n
\n

Hmm…that is surprising that you get back the expected pages when browsing directly but that the dashboard does not.

\n

Can you do the following:

\n \n

Thank you for your patience with all of this. I am really hoping we can get to the bottom of the mystery.

\n
", "votes": null, "replies": [ { "id": 3309472, "author_name": "kellywalker3lc", "author_url": "", "post_date": "10/31/2025 19:26:37", "content": "

You may be interested to see that the other user figured out the cause of the issue. There was an ngrok warning getting in the way.\nhttps://www.kaggle.com/competitions/the-3lc-cotton-weed-detection-challenge/discussion/612346#3309407

\n

I have asked for some more details about the ngrok warning. If/when those are posted, it may help us understand if you are having the same issue.

\n

Also, that user posted a notebook using a different solution - cloudflare instead of ngrok - that you might also use to work around your issue.

", "votes": null, "replies": [ { "id": 3336236, "author_name": "kellywalker3lc", "author_url": "", "post_date": "11/18/2025 12:02:57", "content": "

We have found a bug in the logic that sets the header that allows for bypassing the NGrok warning page. Sometime after we added that original logic, NGrok made it so free accounts use more than one base domain, and we were only checking for one in particular. A fix will be available in the next 3LC Dashboard release, coming in the next couple of days. Sorry for the trouble and for the confusion.

", "votes": null, "replies": [] } ] } ] } ] } ] } ], "raw_markdown_by_id": { "3309005": "I followed the steps given in the link https://github.com/3lc-ai/3lc-with-colab, but still getting the red banner. i am using colob pro but exhausted my limits which will be renewed in couple of days. is the red banner is displyed in the dashboard beacuse of free resources of colob ?", "3309029": "gokulakrishnanp thanks for trying out 3LC, and sorry you have run into trouble.\n\nThe red banner in the dashboard means that it cannot reach the object service, even though your colab screenshot appears to show it is running just fine.\n\nFrom the dashboard screenshot, it looks like the ngrok URL for the object service may have accidentally ended up with an unintentional space in it, i.e. it should start with \"deistic\" and not \"deisti c\". Maybe an extra character was included when copying from the colab terminal?\n\n![](https://www.googleapis.com/download/storage/v1/b/kaggle-forum-message-attachments/o/inbox%2F27793746%2Fb6ee056e74e179dfc98e21703db9b431%2FScreenshot%202025-10-30%20135155.png?generation=1761850442555357&alt=media)\n\nCan you check the address bar and see if there is a space there (either an actual space or perhaps an encoded %20) and remove it if so and press enter? I think the URL you are using for this example would look like:\nhttps://dashboard.3lc.ai/?object_service=https%3A%2F%2Fdeistic-angle-nonprimitively.ngrok-free.dev\n\nNote that when you run the object service again, it will get a different URL from ngrok.", "3309203": "kellywalker3lc Thank you so much for addressing the issue, yes that's correct because of the space. now the red banner is gone after copy pasting it instead of right click 'go to' over the link inside terminal. but still the log got an error \"https://deistic-angle-nonprimitively.ngrok-free.dev/status: Invalid HTTP response (\n Hmm...that is surprising that you get back the expected pages when browsing directly but that the dashboard does not.\n> \n> Can you do the following:\n> - Run the object service using ngrok and loglevel DEBUG as before\n> - Browse to the object service \"live\" and \"status\" endpoints directly and post screenshots of the browser with address and page contents\n> - Open the developer tools network tab\n> - Browse to the dashboard URL (that has object_service=...)\n> - Post a screenshot of the Log window with its errors\n> - Select the requests going to the object service (\"status\" and any pre-flight requests) in the developer tools network tab, inspect the request/response headers, status code, any redirects, and contents if possible; post screenshots of all you can\n> - Post your 3LC log; we should see it serving the \"live\" and \"status\" requests you entered directly but then presumably nothing after since the dashboard requests seem not to make it\n> \n> Thank you for your patience with all of this. I am really hoping we can get to the bottom of the mystery.", "3309472": "You may be interested to see that the other user figured out the cause of the issue. There was an ngrok warning getting in the way.\nhttps://www.kaggle.com/competitions/the-3lc-cotton-weed-detection-challenge/discussion/612346#3309407\n\nI have asked for some more details about the ngrok warning. If/when those are posted, it may help us understand if you are having the same issue.\n\nAlso, that user posted a notebook using a different solution - cloudflare instead of ngrok - that you might also use to work around your issue.", "3336236": "We have found a bug in the logic that sets the header that allows for bypassing the NGrok warning page. Sometime after we added that original logic, NGrok made it so free accounts use more than one base domain, and we were only checking for one in particular. A fix will be available in the next 3LC Dashboard release, coming in the next couple of days. Sorry for the trouble and for the confusion." }, "source": "meta" }