A clear and concise description of what the bug is.
This is kinda weird. I have been using metamask to send ETH without issues over the last year. However, today I wanted to send some Rinkeby ETH to another address and then I noticed that the transaction fee section keeps loading indefinitely, and with this happening the transaction cannot be successful. I thought it was my network. Every other website is opening fast and normal. I even restarted the browser, it's the same.
What could be the issue, please?
Attached is a screenshot.
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
It should show the transaction fee to send ETH to another wallet address so that the transaction would be successful.
Screenshots

Browser details:
An issue with the Transaction Fee loading could be the API, Ethgasstation, we're using to estimate those three fees. Some possibilities of this issue could be:
To determine #2 is the case open the extension UI console by right-clicking the above view and Inspect on the menu. When the console is opened, select the Network tab at the top to view the network calls. The ethgasAPI.json should be the network call, if you don't see this try sending a new tx within the extension. Select the ethgasAPI.json and it should return the details of the network call, we are looking to the status code. A status code of 4xx (400, 401, 403) would signify #2. Status codes of 5xx would would signify #1.
For an immediate work around, enabling Advanced gas controls would allow you to enter the appropriate gas price/limit for your transactions. Click the Account Icon in the top-right -> Settings -> Advanced -> Scroll down half way and toggle Advanced gas controls.
Internally, we should detect when the gas API is down/blocked and handle this appropriately. Possibly would render the Advanced Gas Controls in these cases.
Looks like this is probably an issue from 7.7.0.1, but it has been fixed in 7.7.1, which should auto update soon for all users.
@tmashuang i think https://ethgasstation.info/json/ethgasAPI.json is down and cannot be accessed.
I was able fix and send a transaction successfully this by using your workaround here
Thanks!