Google Chrome
Step 1: Open the console
- Open a Chrome browser
- Click on the three dots menu in the top right corner
- Click on More Tools
- Click on Developer Tools
- Click on Console in the panel that opens
Step 2: Select the Settings
- Press the Gear in the top right corner to open the Settings menu.
- Scroll down to Console and check the boxes for Preserve log upon navigation, and Show timestamps
- Click the small close x in the preferences window to return to the console
Step 3: Clear the console log file
- Click on the Clear console icon (circle with a diagonal line) on the left side to erase the current log.
Step 4: Recreate the issue you are experiencing
- Whatever issue you are encountering, having a clear log, please try and re-create the issue. Doing so will log what is happening and allow support to help.
Step 5: Save the log and submit it to support
- Right-click in the Console and click Save as and provide a file name like "chromelog-yourname.txt"
- Send the saved log file to support via your open ticket or email help@propeller.cloud
Firefox
Step 1: Open the Console
- Open a Firefox browser window
- On your keyboard: press Ctrl+Alt+I (or Cmd+Option+I on a Mac). You can also click the top-right menu, click More Tools, then select Web Developer, and then select Web Console.
Step 2: Select the Settings
- In the Console, click the gear, and then check the Persist Logs and Enable Timestamps
Step 3: Clear the console log file
- Click on the Console tab, then click on the trashcan icon to clear the log history
Step 4: Recreate the issue you are experiencing
- Whatever issue you are encountering, having a clear log, please try and re-create the issue. Doing so will log what is happening and allow support to help.
Step 5: Save the log and submit it to support
- Right-click on the console text and select Export visible messages to clipboard
- Save the document and provide a file name like "firefoxlog-yourname.txt"
- Send the saved log file to support via your open ticket or email help@propeller.cloud
Comments
0 comments
Article is closed for comments.