Question

website content didn't display after deploying with DigitalOcean Control Panel

Posted on January 18, 2024
DigitalOcean App Platform
Asked by Jeff Xu

I create web APP with DigitalOcean Control Panel, deploy succefully, and control panel provides website url, after clicking the website url, I only could see the website head, can’t see any content. I could see the content if I deploy it with local machine.The website url is https://seahorse-app-9izjz.ondigitalocean.app/. Please help check it . Thanks!

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

KFSys

Site Moderator

• January 18, 2024

Heya,

Can you confirm how you deployed the website? What steps did you take?

Additionally, do you see anything in the logs?

One other thing, when I check the website’s console, I can see a lot of errors related to Javascript and other similar stuff like:

alchemyContext.ts:54 Uncaught Error: Alchemy URL protocol must be one of http, https, ws, or wss. Recieved: undefined
    at makeAlchemyContext (alchemyContext.ts:54:1)
    at createAlchemyWeb3 (index.ts:167:1)
    at Module.<anonymous> (interact.js:5:1)
    at ./src/utils/interact.js (interact.js:142:1)
    at __webpack_require__ (bootstrap:856:1)
    at fn (bootstrap:150:1)
    at Module.<anonymous> (App.js:13:1)
    at ./src/Minter.js (Minter.js:106:1)
    at __webpack_require__ (bootstrap:856:1)
    at fn (bootstrap:150:1)
    at Module.<anonymous> (App.css:82:1)
    at ./src/App.js (App.js:13:1)
    at __webpack_require__ (bootstrap:856:1)
    at fn (bootstrap:150:1)
    at Module.<anonymous> (index.css:82:1)
    at ./src/index.js (index.js:18:1)
    at __webpack_require__ (bootstrap:856:1)
    at fn (bootstrap:150:1)
    at 1 (pinata.js:32:1)
    at __webpack_require__ (bootstrap:856:1)
    at checkDeferredModules (bootstrap:45:1)
    at Array.webpackJsonpCallback [as push] (bootstrap:32:1)
    at main.chunk.js:1:73
webpackHotDevClient.js:138 src/Minter.js
  Line 30:11:  Using target="_blank" without rel="noreferrer" (which implies rel="noopener") is a security risk in older browsers: see https://mathiasbynens.github.io/rel-noopener/#recommendations                                                                                                                                                                                                                          react/jsx-no-target-blank
  Line 39:13:  Effect callbacks are synchronous to prevent race conditions. Put the async function inside:

useEffect(() => {
  async function fetchData() {
    // You can await here
    const response = await MyAPI.getData(someId);
    // ...
  }
  fetchData();
}, [someId]); // Or [] if effect doesn't need props or state

Learn more about data fetching with Hooks: https://reactjs.org/link/hooks-data-fetching  react-hooks/exhaustive-deps

src/utils/interact.js
  Line 35:15:  Using target="_blank" without rel="noreferrer" (which implies rel="noopener") is a security risk in older browsers: see https://mathiasbynens.github.io/rel-noopener/#recommendations  react/jsx-no-target-blank
  Line 77:13:  Using target="_blank" without rel="noreferrer" (which implies rel="noopener") is a security risk in older browsers: see https://mathiasbynens.github.io/rel-noopener/#recommendations  react/jsx-no-target-blank
  Line 91:18:  Expected '===' and instead saw '=='                                                                                                                                                    eqeqeq
  Line 91:40:  Expected '===' and instead saw '=='                                                                                                                                                    eqeqeq
  Line 91:68:  Expected '===' and instead saw '=='                                                                                                                                                    eqeqeq
  Line 99:20:  The object literal notation {} is preferrable                                                                                                                                          no-new-object
printWarnings @ webpackHotDevClient.js:138
VM17:2 Uncaught ReferenceError: process is not defined
    at 4043 (<anonymous>:2:13168)
    at r (<anonymous>:2:306599)
    at 8048 (<anonymous>:2:9496)
    at r (<anonymous>:2:306599)
    at 8641 (<anonymous>:2:1379)
    at r (<anonymous>:2:306599)
    at <anonymous>:2:315627
    at <anonymous>:2:324225
    at <anonymous>:2:324229
    at e.onload (index.js:1:1)